Documentation/core-api/workqueue.rst

106 things like CPU locality, concurrency limits, priority and more.  To
188   This flag is the right choice when cpu locality is important.
198   possible.  Unbound wq sacrifices locality but is useful for
373   level of locality in wq operations and work item execution.
380 cache locality. For example, if a workqueue is using the default affinity
434   locality while still being able to utilize other CPUs if necessary and
449 kernel, there exists a pronounced trade-off between locality and utilization
452 Higher locality leads to higher efficiency where more work is performed for
453 the same number of consumed CPU cycles. However, higher locality may also
475 execution locality matter between the issuer and ``kcryptd``. The following
503 locality.
582 Now, the tradeoff between locality and utilization is clearer. "cache" shows