Lines Matching full:scope

353 An unbound workqueue groups CPUs according to its affinity scope to improve
355 scope of "cache", it will group CPUs according to last level cache
358 Once started, the worker may or may not be allowed to move outside the scope
359 depending on the ``affinity_strict`` setting of the scope.
364   Use the scope in module parameter ``workqueue.default_affinity_scope``
379   cases. This is the default affinity scope.
388 The default affinity scope can be changed with the module parameter
390 scope can be changed using ``apply_workqueue_attrs()``.
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.
399   When default is the current scope, reading this file will also show the
400   current effective scope in parentheses, for example, ``default (cache)``.
405   that the worker is inside its affinity scope, which is called
407   anywhere in the system as it sees fit. This enables benefiting from scope
411   If set to 1, all workers of the scope are guaranteed always to be in the
412   scope. This may be useful when crossing affinity scopes has other
414   isolation. Strict NUMA scope can also be used to match the workqueue
451 scope settings on ``kcryptd`` measured over five runs. Bandwidths are in
518 Eight issuers moving around over four L3 cache scope still allow "cache
564 scope over "system" is, while consistent and noticeable, small. However, the
571 affinity scope for unbound pools.
578 * An unbound workqueue with strict "cpu" affinity scope behaves the same as
583   behavior, use strict "numa" affinity scope.