Lines Matching defs:it
77 * without an RT task running, it can cause RT tasks to
762 * Ensure this RQ takes back all the runtime it lend to its neighbours.
919 * can be time-consuming. Try to avoid it when possible.
1039 * In case we did anyway, make it go away,
1040 * replenishment is a joke, since it will replenish us
1453 * and force it to run for a likely small time after the RT wakee is
1562 * task is a higher priority, then it will stay on this CPU
1566 * around just because it gave up its CPU, perhaps for a
1569 * For equal prio tasks, we just let the scheduler sort it out.
1571 * Otherwise, just let it ride on the affined RQ and the
1574 * This test is optimistic, if we get it wrong the load-balancer
1575 * will have to sort it out.
1577 * We take into account the capacity of the CPU to ensure it fits the
1602 * Don't bother moving it if the destination CPU is
1628 * p is migratable, so let's not schedule it and
1629 * see if it is pushed or pulled somewhere else.
1648 * This is OK, because current is on_cpu, which avoids it being
1650 * disabled avoiding further scheduler activity on it and we've
1765 * if it is still active
1943 * If the preivous CPU has same load, keep it as
1951 * If candidate CPU is the previous CPU, select it.
2023 * it is most likely cache-hot in that location.
2098 /* Will lock the rq it finds */
2137 /* If this rq is still suitable use it. */
2194 * so it is possible that next_task has migrated.
2205 * to push it to. Do not retry in this case, since
2241 /* push_rt_task will return true if it moved an RT */
2254 * tasks queued on it (overloaded) needs to be notified that a CPU has opened
2275 * When a CPU schedules a lower priority task, it will kick off the
2277 * As it only takes the first CPU that schedules a lower priority task
2300 * If rto_next_cpu() is called with rto_cpu is a valid CPU, it
2362 * The rto_cpu is updated under the lock, if it has a valid CPU
2365 * Otherwise it is finishing up and an ipi needs to be sent.
2392 * When it gets updated, a check is made if a push is possible.
2489 * p if it is lower in priority than the
2654 * This task is not running, but if it is
2885 struct css_task_iter it;
2895 css_task_iter_start(&tg->css, 0, &it);
2896 while (!ret && (task = css_task_iter_next(&it))) {
2899 css_task_iter_end(&it);
2992 * Disallowing the root group RT runtime is BAD, it would disallow the