Lines Matching full:affinity

376 Affinity Scopes
379 An unbound workqueue groups CPUs according to its affinity scope to improve
380 cache locality. For example, if a workqueue is using the default affinity
387 Workqueue currently supports the following affinity scopes.
411   This is the default affinity scope.
420 The default affinity scope can be changed with the module parameter
421 ``workqueue.default_affinity_scope`` and a specific workqueue's affinity
424 If ``WQ_SYSFS`` is set, the workqueue will have the following affinity scope
429   Read to see the current affinity scope. Write to change.
435   0 by default indicating that affinity scopes are not strict. When a work
437   that the worker is inside its affinity scope, which is called
444   scope. This may be useful when crossing affinity scopes has other
450 Affinity Scopes and Performance
461 enough across the affinity scopes by the issuers. The following performance
482 are the read bandwidths and CPU utilizations depending on different affinity
490    * - Affinity
529    * - Affinity
572    * - Affinity
595 In the above experiments, the efficiency advantage of the "cache" affinity
603 affinity scope for unbound pools.
610 * An unbound workqueue with strict "cpu" affinity scope behaves the same as
614 * Affinity scopes are introduced in Linux v6.5. To emulate the previous
615   behavior, use strict "numa" affinity scope.
617 * The loss of work-conservation in non-strict affinity scopes is likely
627 Use tools/workqueue/wq_dump.py to examine unbound CPU affinity
631   Affinity Scopes