[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <aacf48f5db89f6f2336f1a4463ae3a24@mail.gmail.com>
Date: Tue, 18 Jul 2017 11:12:53 -0700
From: Alexei Potashnik <alexei@...estorage.com>
To: tj@...nel.org
Cc: linux-kernel@...r.kernel.org
Subject: [PATCH] workqueue: doc change for ST behavior on NUMA systems
NUMA rework of workqueue made the combination of max_active of 1 and
WQ_UNBOUND insufficient to guarantee ST behavior system wide.
alloc_ordered_queue should now be used instead.
Signed-off-by: Alexei Potashnik <alexei@...estorage.com>
---
Documentation/core-api/workqueue.rst | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/Documentation/core-api/workqueue.rst
b/Documentation/core-api/workqueue.rst
index ffdec94..3943b5b 100644
--- a/Documentation/core-api/workqueue.rst
+++ b/Documentation/core-api/workqueue.rst
@@ -243,11 +243,15 @@ throttling the number of active work items,
specifying '0' is
recommended.
Some users depend on the strict execution ordering of ST wq. The
-combination of ``@..._active`` of 1 and ``WQ_UNBOUND`` is used to
-achieve this behavior. Work items on such wq are always queued to the
-unbound worker-pools and only one work item can be active at any given
+combination of ``@..._active`` of 1 and ``WQ_UNBOUND`` used to
+achieve this behavior. Work items on such wq were always queued to the
+unbound worker-pools and only one work item could be active at any given
time thus achieving the same ordering property as ST wq.
+In the current implementation the above configuration only guarantees
+ST behavior within a given NUMA node. Instead alloc_ordered_queue should
+be used to achieve system wide ST behavior.
+
Example Execution Scenarios
===========================
--
1.9.1
Powered by blists - more mailing lists