Sorry I'm late according to going out. On Tue, Jun 30, 2009 at 6:30 PM, Sven-Thorsten Dietrich<sven@xxxxxxxxxxxxxxxxxxxxx> wrote: > I that was a single CPU scenario. > For testing on SMP, the cyclictest threads need to behave identicallly > (even in priority) on all CPUs. Additionally, I want you to consider both Unicore and Multicore when some users will use -h option. > That same argument also applies to this patch, doesn't it? > In other words, without changing the existing code, you could change the > prios for the histogram mode via a similar script, right? Yes, It's right. But. I am talking about output style of prios to avoid confusion between without -h and with -h. As you know, Cyclictest display result of latencies on the console without detailed explanation. So, When we add -h option to get histogram data, Most users have to view source code because of the different output style suddenly. > I don't disagree, but I think the proper fix may be to decouple > histogram from priority, via another parameter. > > Note that the thread interval is also held constant when histogram is > configured -- not just the priority. > > if (!histogram) /* histogram requires same interval on CPUs*/ > interval += distance; > > > The patch you sent basically reverts a bug-fix for the histogram > application on SMP, but doesn't change the interval behavior. > > So you would also have to decouple the interval code as well. Thank you for explanation of histogram related patches like priority and interval. If you accept my proposal to avoid confusion of output style, I want to change interval code reversely . -:) But, If you and others don't agree with my opinions, I think that We have to append additional explanation in the "#> cyclictest --help" to understand output using -h option at least like belows. before) "-h --histogram=US dump a latency histogram to stdout after the run\n" after ) "-h --histogram=US dump a latency histogram to stdout after the run (with same priority about threads)\n" How about you think this my opinions? > It would be better to be able to explicitly set priorities and intervals > to be the same, when distributed per-CPU on SMP. That is one kind of > test, which is important. > > Inversely relating priority versus interval on UP is another kind of > test. This seems to be what you are trying to do. > > So to have both, means you can to stack threads on SMP and have multiple > threads on each CPU, operating at increasing intervals. Each thread > would report data. > > But that implies a 3-D table to log the data returned from cyclictest > threads at lower priorities (lower than the highest priority). > > The histogram code is only able to log one set of data for each thread > as it is today. > > And as-is, the histogram assumes threads are distributed per-cpu via > affinity on SMP. Changing to a 3-D matrix is interesting, but how would > you represent that / store ? > > What exactly are you testing / looking for? I want to test maximum latencies based on background stress conditions on SMP. And, I want to get histogram data about worstcase latencies using -h option. -- Regards, GeunSik Lim ( Samsung Electronics ) Blog : http://blog.naver.com/invain/ e-Mail: geunsik.lim@xxxxxxxxxxx leemgs@xxxxxxxxx , leemgs1@xxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
