Searched refs:imbalance (Results 1 – 14 of 14) sorted by relevance
| /openbmc/linux/kernel/sched/ |
| H A D | fair.c | 1374 adjust_numa_imbalance(int imbalance, int dst_running, int imb_numa_nr) in adjust_numa_imbalance() argument
1377 * Allow a NUMA imbalance if busy CPUs is less than the maximum in adjust_numa_imbalance()
1384 return imbalance; in adjust_numa_imbalance()
1387 * Allow a small imbalance based on a simple pair of communicating in adjust_numa_imbalance()
1390 if (imbalance <= NUMA_IMBALANCE_MIN) in adjust_numa_imbalance()
1393 return imbalance; in adjust_numa_imbalance()
2268 * not address the load imbalance and helps one task at in task_numa_compare()
2398 * imbalance that would be overruled by the load balancer. in task_numa_find_cpu()
2401 unsigned int imbalance; in task_numa_find_cpu() local
2405 * Would movement cause an imbalance in task_numa_find_cpu()
8796 long imbalance; global() member
9847 long imbalance; sibling_imbalance() local
10341 unsigned long imbalance; find_idlest_group() local
[all...] |
| H A D | sched.h | 1893 int imbalance; /* XXX unrelated to capacity but shared group state */ member
|
| /openbmc/linux/Documentation/dev-tools/ |
| H A D | sparse.rst | 73 sparse would otherwise report a context imbalance.
|
| /openbmc/linux/tools/perf/Documentation/ |
| H A D | perf-stat.txt | 299 is a useful mode to detect imbalance between sockets. To enable this mode,
306 is a useful mode to detect imbalance between dies. To enable this mode,
321 is a useful mode to detect imbalance between physical cores. To enable this mode,
331 is a useful mode to detect imbalance between NUMA nodes. To enable this
|
| /openbmc/linux/Documentation/scheduler/ |
| H A D | sched-domains.rst | 52 to our runqueue. The exact number of tasks amounts to an imbalance previously
|
| /openbmc/linux/Documentation/trace/ |
| H A D | events-kmem.rst | 96 refills and drains could imply an imbalance between CPUs where too much work
|
| /openbmc/linux/Documentation/mm/ |
| H A D | numa.rst | 103 Thus, under sufficient imbalance, tasks can migrate between nodes, remote
|
| /openbmc/linux/Documentation/admin-guide/mm/ |
| H A D | memory-hotplug.rst | 573 Having too much system RAM managed by ZONE_MOVABLE is called a zone imbalance,
611 allocations and silently create a zone imbalance, usually triggered by
|
| H A D | hugetlbpage.rst | 320 undesirable imbalance in the distribution of the huge page pool, or
|
| /openbmc/u-boot/scripts/ |
| H A D | spelling.txt | 571 imblance||imbalance
|
| /openbmc/linux/scripts/ |
| H A D | spelling.txt | 778 imblance||imbalance
|
| /openbmc/linux/Documentation/networking/ |
| H A D | scaling.rst | 188 to the same CPU is CPU load imbalance if flows vary in packet rate.
|
| /openbmc/linux/Documentation/process/ |
| H A D | coding-style.rst | 335 problem, which is called the function-growth-hormone-imbalance syndrome.
|
| /openbmc/linux/arch/x86/ |
| H A D | Kconfig | 2531 Enable call/ret counters for imbalance detection and build in
|