Lines Matching full:tasks

18  * of this group and it would create no effect on tasks in other group. So a
21  * Even if task is run with different nice value it will affect the tasks in
43 tasks in different groups on the basis of the shares assigned to that group.
46 number of tasks in that group(in this case only 1).
51 respectively. Hence if the tasks are running infinitely they are supposed to
67 of system default tasks which can run any time.
93 Renice all tasks of a group to -20 and let tasks in all other groups run with
99 In this test for the first run the test is run with say n tasks in m groups.
103 Test 06-08 : NUM GROUPS vs NUMBER of TASKS TEST
105 In the following three testcases a total tasks are same and each task is
109 Test 06:      N X M (N groups with M tasks each)
115 Test 08:      1 X N*M (1 group with N*M tasks)
121 each running a large number of tasks in it.
129 In this test one group has very less tasks while others have large number of
130 tasks. This tests if fairness still remains.
139 In the following two testcases we run n(NUM_TASKS set in script) tasks as the
140 load tasks which simply hog the cpu by doing some sqrt calculation of a number
141 of type double. A task named latency check task is launched after these tasks.
145 In case of test 12 the tasks are running under different groups created
147 NUM_CPUS). The tasks migrate to their groups automatically, before they start
158 is mounted, and has tasks in different groups.
179  exp:- expected time as per the shares of the group and num of tasks in group.