Lines Matching full:affinity

350 Affinity Scopes
353 An unbound workqueue groups CPUs according to its affinity scope to improve
354 cache locality. For example, if a workqueue is using the default affinity
361 Workqueue currently supports the following affinity scopes.
379   cases. This is the default affinity scope.
388 The default affinity scope can be changed with the module parameter
389 ``workqueue.default_affinity_scope`` and a specific workqueue's affinity
392 If ``WQ_SYSFS`` is set, the workqueue will have the following affinity scope
397   Read to see the current affinity scope. Write to change.
403   0 by default indicating that affinity scopes are not strict. When a work
405   that the worker is inside its affinity scope, which is called
412   scope. This may be useful when crossing affinity scopes has other
418 Affinity Scopes and Performance
429 enough across the affinity scopes by the issuers. The following performance
450 are the read bandwidths and CPU utilizations depending on different affinity
458    * - Affinity
497    * - Affinity
540    * - Affinity
563 In the above experiments, the efficiency advantage of the "cache" affinity
571 affinity scope for unbound pools.
578 * An unbound workqueue with strict "cpu" affinity scope behaves the same as
582 * Affinity scopes are introduced in Linux v6.5. To emulate the previous
583   behavior, use strict "numa" affinity scope.
585 * The loss of work-conservation in non-strict affinity scopes is likely
595 Use tools/workqueue/wq_dump.py to examine unbound CPU affinity
599   Affinity Scopes