Lines Matching full:affinity

370 Affinity Scopes
373 An unbound workqueue groups CPUs according to its affinity scope to improve
374 cache locality. For example, if a workqueue is using the default affinity
381 Workqueue currently supports the following affinity scopes.
399   cases. This is the default affinity scope.
408 The default affinity scope can be changed with the module parameter
409 ``workqueue.default_affinity_scope`` and a specific workqueue's affinity
412 If ``WQ_SYSFS`` is set, the workqueue will have the following affinity scope
417   Read to see the current affinity scope. Write to change.
423   0 by default indicating that affinity scopes are not strict. When a work
425   that the worker is inside its affinity scope, which is called
432   scope. This may be useful when crossing affinity scopes has other
438 Affinity Scopes and Performance
449 enough across the affinity scopes by the issuers. The following performance
470 are the read bandwidths and CPU utilizations depending on different affinity
478    * - Affinity
517    * - Affinity
560    * - Affinity
583 In the above experiments, the efficiency advantage of the "cache" affinity
591 affinity scope for unbound pools.
598 * An unbound workqueue with strict "cpu" affinity scope behaves the same as
602 * Affinity scopes are introduced in Linux v6.5. To emulate the previous
603   behavior, use strict "numa" affinity scope.
605 * The loss of work-conservation in non-strict affinity scopes is likely
615 Use tools/workqueue/wq_dump.py to examine unbound CPU affinity
619   Affinity Scopes