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 +---------- +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. +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. + +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. + +Test 12: cpuctl latency test 2 +------- +This test adds one testcase for testing the latency when the group scheduler +is mounted, and has tasks in differnet groups. + +NOTE: There is no clear consensus on the maximum latency that the scheduler +should guarantee. Latency may vary from few milliseconds in normal desktops +to even a minute in virtaul guests. However a latency of more than 20 ms +(under normal load, as it is load dependent) is not considered good. +This test is to keep an eye on the max latency in different kernel versions +with respect to further development of the group scheduler. So even if the +test may show FAIL, it may not be an actual failure. + ( - In all tests calc cpu time and exp cpu time should be same + In all(1-10) tests calc cpu time and exp cpu time should be same Time:: calc:- calculated cpu time obtained for a running task exp:- expected time as per the shares of the group and num of tasks in group. ) ------------------------------------------------------------------------------ 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
