On Mon, Dec 15, 2008 at 12:59:06PM +0530, Sudhir Kumar wrote: > Add some documentation with respect to test. > > Signed-off-by: Sudhir Kumar <[email protected]> > > Index: > ltp-full-20081130/testcases/kernel/controllers/cpuctl/cpuctl_testplan.txt > =================================================================== > --- > ltp-full-20081130.orig/testcases/kernel/controllers/cpuctl/cpuctl_testplan.txt > +++ ltp-full-20081130/testcases/kernel/controllers/cpuctl/cpuctl_testplan.txt > @@ -130,8 +130,39 @@ In this test one group has very less tas > tasks. This tests if fairness still remains. > > > +Test 11-12: LATENCY TESTS > +----------
A one-liner to say what LATENCY TESTS are before explaining (as below) how they do it ? > +In the following two testcases we run n(NUM_TASKS set in script) tasks as the > +load tasks which simply hog the cpu by doing some sqrt calculation of a > double > +number. A task named latency check task is launched after these tasks. This > +task goes for frequent sleeps and notice the time before and after sleep. It > +then checks the difference in the two times and then compares this with the > +expected sleep time. Do you want to be so verbose and explain about "time before and after sleep" ? I think you could reduce the description here. Just say that the latency check task sleeps frequently and measures the latency as the difference b/n the actual and expected sleep durations. > +In case of test 12 the tasks are running under different groups created > +dynamically depending on the number of cpus in the machine.(min 2, else 1.5 * > +NUM_CPUS). The tasks migrate to their groups automatically, before they start > +hogging the cpu. The latency check task also runs under any of the groups. Again, I am not sure if we need this verbose description of the test cases. May be I say that because I have never looked enough into LTP code. So ignore me here. > + > +Test 11: cpuctl latency test 1 > +------- > +This test adds one testcase for testing the latency when the group scheduler > +is not mounted, but compiled in kernel. What do you mean by saying "group scheduler is not mounted" ? Do you mean to say "Group scheduling compiled into the kernel but no groups created" ? Regards, Bharata. ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
