Remove the general not-updated warning for perf-tuning,

since the document is mostly accurate.  But since the
accept-mutex section seems a little dated, leave a
warning there.  That could use some developer intervention.

Also, remove the author attribution, since large parts
of this have changed since Dean wrote it.

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

diff --git a/docs/manual/misc/perf-tuning.html.en b/docs/manual/misc/perf-tuning.html.en
index 6e55571cb5bc3de71dd66bff12656c03d5a32158..fbaa8e76188f18aab163bab44f4c3cd50feeb1ce 100644 (file)
--- a/docs/manual/misc/perf-tuning.html.en
+++ b/docs/manual/misc/perf-tuning.html.en
@@ -22,15 +22,6 @@
 </div>
 
 
-    <div class="warning"><h3>Warning:</h3>
-      <p>This document has not been fully updated
-      to take into account changes made in the 2.0 version of the
-      Apache HTTP Server. Some of the information may still be
-      relevant, but please use it with care.</p>
-    </div>
-
-    <p>Orignally written by Dean Gaudet.</p>
-
     <p>Apache 2.0 is a general-purpose webserver, designed to
     provide a balance of flexibility, portability, and performance.
     Although it has not been designed specifically to set benchmark
@@ -544,6 +535,13 @@
 
       
 
+    <div class="warning"><h3>Warning:</h3>
+      <p>This section has not been fully updated
+      to take into account changes made in the 2.0 version of the
+      Apache HTTP Server. Some of the information may still be
+      relevant, but please use it with care.</p>
+    </div>
+
       <p>This discusses a shortcoming in the Unix socket API. Suppose
       your web server uses multiple <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> statements to listen on either multiple
       ports or multiple addresses. In order to test each socket
@@ -674,6 +672,9 @@
       <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>
       directives.</p>
 
+      <p>The directive <code class="directive"><a href="../mod/mpm_common.html#acceptmutex">AcceptMutex</a></code> can be used to
+      change the selected mutuex implimentation at run-time.</p>
+
       <dl>
         <dt><code>USE_FLOCK_SERIALIZED_ACCEPT</code></dt>
 

diff --git a/docs/manual/misc/perf-tuning.xml b/docs/manual/misc/perf-tuning.xml
index cced9756d1cc824bc641756c357a31abe319021f..6a751ebf4887aa98d5c23e16ce30bf9f30d1aa10 100644 (file)
--- a/docs/manual/misc/perf-tuning.xml
+++ b/docs/manual/misc/perf-tuning.xml
@@ -9,15 +9,6 @@
 
   <summary>
 
-    <note type="warning"><title>Warning:</title>
-      <p>This document has not been fully updated
-      to take into account changes made in the 2.0 version of the
-      Apache HTTP Server. Some of the information may still be
-      relevant, but please use it with care.</p>
-    </note>
-
-    <p>Orignally written by Dean Gaudet.</p>
-
     <p>Apache 2.0 is a general-purpose webserver, designed to
     provide a balance of flexibility, portability, and performance.
     Although it has not been designed specifically to set benchmark
@@ -557,6 +548,13 @@
 
       <title>accept Serialization - multiple sockets</title>
 
+    <note type="warning"><title>Warning:</title>
+      <p>This section has not been fully updated
+      to take into account changes made in the 2.0 version of the
+      Apache HTTP Server. Some of the information may still be
+      relevant, but please use it with care.</p>
+    </note>
+
       <p>This discusses a shortcoming in the Unix socket API. Suppose
       your web server uses multiple <directive module="mpm_common"
       >Listen</directive> statements to listen on either multiple
@@ -689,6 +687,10 @@
       <directive module="mpm_common">Listen</directive>
       directives.</p>
 
+      <p>The directive <directive
+      module="mpm_common">AcceptMutex</directive> can be used to
+      change the selected mutuex implimentation at run-time.</p>
+
       <dl>
         <dt><code>USE_FLOCK_SERIALIZED_ACCEPT</code></dt>