LUDOC-394 manual: Add meaningful ref names under BenchmarkingTests.xml

This patch adds meaningful and proper reference name under file
BenchmarkingTests.xml

Signed-off-by: Arshad Hussain <arshad.hussain@aeoncomputing.com>
Change-Id: I44fda9a62045d2f97c843f245a32ff6df7d21713
Reviewed-on: https://review.whamcloud.com/43438
Tested-by: jenkins <devops@whamcloud.com>
Reviewed-by: Andreas Dilger <adilger@whamcloud.com>

diff --git a/BenchmarkingTests.xml b/BenchmarkingTests.xml
index 5cc0177..2a98501 100644 (file)
--- a/BenchmarkingTests.xml
+++ b/BenchmarkingTests.xml
@@ -309,7 +309,7 @@
         required) and creates one instance of <literal>echo_client</literal> for
         each <literal>obdfilter</literal> instance in order to generate I/O
         requests directly to the OST.</para>
-        <para>For more details, see <xref linkend="dbdoclet.50438212_59319"/>.
+        <para>For more details, see <xref linkend="local_disk_performance"/>.
         </para>
       </listitem>
       <listitem>
@@ -369,7 +369,7 @@
       particular, pay attention to the listed maximum values listed for each
       parameter in the script.</para>
     </note>
-    <section xml:id="dbdoclet.50438212_59319">
+    <section xml:id="local_disk_performance">
       <title><indexterm><primary>benchmarking</primary>
         <secondary>local disk</secondary></indexterm>
       Testing Local Disk Performance</title>
@@ -776,7 +776,7 @@ lustre-OST0001-osc-ffff88007754bc00&quot; sh obdfilter-survey</screen>
         <para>It is also useful to monitor and record average disk I/O sizes
         during each test using the &apos;disk io size&apos; histogram in the
         file <literal>lctl get_param obdfilter.*.brw_stats</literal>
-        (see <xref linkend="dbdoclet.50438271_55057"/> for details). These
+        (see <xref linkend="monitor_ost_block_io_stream"/> for details). These
         numbers help identify problems in the system when full-sized I/Os are
         not submitted to the underlying disk. This may be caused by problems in
         the device driver or Linux block layer.</para>

diff --git a/LustreProc.xml b/LustreProc.xml
index 4bf356e..e0834b4 100644 (file)
--- a/LustreProc.xml
+++ b/LustreProc.xml
@@ -10,7 +10,7 @@
   file system.  It includes these sections:</para>
   <itemizedlist>
     <listitem>
-      <para><xref linkend="dbdoclet.50438271_83523"/></para>
+      <para><xref linkend="enabling_interpreting_debugging_logs"/></para>
       <para>.</para>
     </listitem>
   </itemizedlist>
@@ -375,7 +375,7 @@ testfs-MDT0000</screen></para>
         <listitem>
           <para><literal>brw_stats</literal> – Histogram data characterizing I/O requests to the
             OSTs. For more details, see <xref xmlns:xlink="http://www.w3.org/1999/xlink"
-              linkend="dbdoclet.50438271_55057"/>.</para>
+              linkend="monitor_ost_block_io_stream"/>.</para>
         </listitem>
         <listitem>
           <para><literal>rpc_stats</literal> – Histogram data showing information about RPCs made by
@@ -993,7 +993,7 @@ PID: 11429
           to that point in the table of calls (<literal>cum %</literal>). </para>
       </section>
     </section>
-    <section xml:id="dbdoclet.50438271_55057">
+    <section xml:id="monitor_ost_block_io_stream">
       <title><indexterm>
           <primary>proc</primary>
           <secondary>block I/O</secondary>
@@ -2639,7 +2639,7 @@ ost.OSS.ost_io.threads_max=256</screen>
     </note>
     <para>See also <xref xmlns:xlink="http://www.w3.org/1999/xlink" linkend="lustretuning"/></para>
   </section>
-  <section xml:id="dbdoclet.50438271_83523">
+  <section xml:id="enabling_interpreting_debugging_logs">
     <title><indexterm>
         <primary>proc</primary>
         <secondary>debug</secondary>