docs: Clarify who dispatches I/O events in motorz PollersPerChild (bz 70105)

The existing wording used "a single child can...dispatch I/O events"
which was ambiguous when the preceding paragraph already said pollers
do the dispatching. Reword to make the subject explicit: each poller
thread independently accepts and dispatches to the worker pool, so
adding pollers parallelizes those operations within a child process.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1935433 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/mod/motorz.xml b/docs/manual/mod/motorz.xml
index 8cefb8e7f1dc6fb90bbbcd46199af601029ac23c..bc6287b16314d045d04e9a329420e63ae32be17c 100644 (file)
--- a/docs/manual/mod/motorz.xml
+++ b/docs/manual/mod/motorz.xml
@@ -235,9 +235,11 @@ LoadModule mpm_motorz_module modules/mod_mpm_motorz.so
     <p>The <directive>PollersPerChild</directive> directive sets the number of
     poller threads created in each child process. Each poller owns its own
     pollset, timer ring and connection-recycle list, and handles a shard of
-    the child's connections, so adding pollers raises the rate at which a
-    single child can accept connections and dispatch I/O events and timer
-    expiries.</p>
+    the child's connections. Because each poller thread independently
+    accepts connections and dispatches ready I/O events and timer
+    expiries to the worker pool, adding pollers raises the rate at which a
+    single child process can handle these operations in parallel rather than
+    serializing them on one poll thread.</p>
 
     <p>A value of <code>0</code> (the default) means <em>auto</em>: the number
     of pollers is derived from the number of online CPUs, capped at a built-in