Lines Matching full:affinity

365 Affinity Scopes
368 An unbound workqueue groups CPUs according to its affinity scope to improve
369 cache locality. For example, if a workqueue is using the default affinity
376 Workqueue currently supports the following affinity scopes.
394   cases. This is the default affinity scope.
403 The default affinity scope can be changed with the module parameter
404 ``workqueue.default_affinity_scope`` and a specific workqueue's affinity
407 If ``WQ_SYSFS`` is set, the workqueue will have the following affinity scope
412   Read to see the current affinity scope. Write to change.
418   0 by default indicating that affinity scopes are not strict. When a work
420   that the worker is inside its affinity scope, which is called
427   scope. This may be useful when crossing affinity scopes has other
433 Affinity Scopes and Performance
444 enough across the affinity scopes by the issuers. The following performance
465 are the read bandwidths and CPU utilizations depending on different affinity
473    * - Affinity
512    * - Affinity
555    * - Affinity
578 In the above experiments, the efficiency advantage of the "cache" affinity
586 affinity scope for unbound pools.
593 * An unbound workqueue with strict "cpu" affinity scope behaves the same as
597 * Affinity scopes are introduced in Linux v6.5. To emulate the previous
598   behavior, use strict "numa" affinity scope.
600 * The loss of work-conservation in non-strict affinity scopes is likely
610 Use tools/workqueue/wq_dump.py to examine unbound CPU affinity
614   Affinity Scopes