Documentation/core-api/workqueue.rst

259 Some users depend on strict execution ordering where only one work item
346 * Unless strict ordering is required, there is no need to use ST wq.
418   0 by default indicating that affinity scopes are not strict. When a work
429   isolation. Strict NUMA scope can also be used to match the workqueue
485    * - cache (strict)
490 "cache", strict or otherwise. All three configurations saturate the whole
524    * - cache (strict)
534 (strict)" to mostly saturate the machine but the loss of work conservation
567    * - cache (strict)
584 better than "cache (strict)" and maximizing workqueue utilization is
593 * An unbound workqueue with strict "cpu" affinity scope behaves the same as
598   behavior, use strict "numa" affinity scope.
600 * The loss of work-conservation in non-strict affinity scopes is likely