Lines Matching defs:busy
1414 * Allow a NUMA imbalance if busy CPUs is less than the maximum
1418 * the number of busy CPUs due to sched_setaffinity.
3524 * we (mostly) drive the selection from busy threads and that the
7467 * If we're busy, the assumption that the last idle period
7733 * previously-executed tasks, which helps better deduce how busy a CPU will
7897 * Compute the task busy time for compute_energy(). This time cannot be
7924 * Compute the perf_domain (PD) busy time for compute_energy(). Based on the
7941 * Set @eenv busy time for the PD that spans @pd_cpus. This busy time can't
8952 * Balance SMT group that's fully busy. Can benefit from migration
8953 * a task on SMT with busy sibling to another CPU on idle core.
9698 unsigned int group_smt_balance; /* Task on busy SMT be moved */
10024 * can only do it if @group is an SMT group and has exactly on busy CPU. Larger
10043 * busy sibling.
10312 * choose has spare or fully busy handling.
10321 * Select the fully busy group with highest avg_load. In
10521 * Computing avg_load makes sense only when group is fully busy or
10583 * find_idlest_group() finds and returns the least busy CPU group within the
11039 * Local is fully busy but has to take more load to relieve the
11107 * nr_idle : dst_cpu is not busy and the number of idle CPUs is quite
11134 /* There is no busy sibling group to pull tasks from */
11216 * busy, let another idle CPU try to pull task.
11325 * SMT cores with more than one busy sibling.
11417 * ASYM_PACKING needs to force migrate tasks from busy but lower
11422 * If @env::src_cpu is an SMT core with busy siblings, let
11523 * Don't balance to idle SMT in busy core right away when
11548 /* Are we the first idle CPU with busy siblings? */
11841 * Reduce likelihood of busy balancing at higher domains racing with
12049 int busy = idle != CPU_IDLE && !sched_idle_cpu(cpu);
12078 interval = get_sd_balance_interval(sd, busy);
12094 busy = idle != CPU_IDLE && !sched_idle_cpu(cpu);
12097 interval = get_sd_balance_interval(sd, busy);
12135 * - When one of the busy CPUs notice that there may be an idle rebalancing
12218 * busy tick after returning from idle, we will update the busy stats.
12310 * other CPUs are idle). We can't really know from here how busy