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

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

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

diff --git a/ConfigurationFilesModuleParameters.xml b/ConfigurationFilesModuleParameters.xml
index aadc0ad..7a58198 100644 (file)
--- a/ConfigurationFilesModuleParameters.xml
+++ b/ConfigurationFilesModuleParameters.xml
@@ -6,13 +6,13 @@
   <para>This section describes configuration files and module parameters and includes the following sections:</para>
   <itemizedlist>
     <listitem>
   <para>This section describes configuration files and module parameters and includes the following sections:</para>
   <itemizedlist>
     <listitem>

-      <para><xref linkend="dbdoclet.50438293_15350"/></para>
+      <para><xref linkend="dbdoclet.tuning_lnet_mod_params"/></para>

     </listitem>
     <listitem>
       <para><xref linkend="dbdoclet.50438293_78010"/></para>
     </listitem>
   </itemizedlist>
     </listitem>
     <listitem>
       <para><xref linkend="dbdoclet.50438293_78010"/></para>
     </listitem>
   </itemizedlist>

-  <section xml:id="dbdoclet.50438293_15350">
+  <section xml:id="dbdoclet.tuning_lnet_mod_params">

       <title>
           <indexterm><primary>configuring</primary></indexterm>
           <indexterm><primary>LNet</primary><see>configuring</see></indexterm>
       <title>
           <indexterm><primary>configuring</primary></indexterm>
           <indexterm><primary>LNet</primary><see>configuring</see></indexterm>

diff --git a/ConfiguringLNet.xml b/ConfiguringLNet.xml
index 2225633..b7868fd 100755 (executable)
--- a/ConfiguringLNet.xml
+++ b/ConfiguringLNet.xml
@@ -446,7 +446,7 @@ route:
         </indexterm>Showing routing information</title>
       <para>When routing is enabled on a node, the tiny, small and large
       routing buffers are allocated. See <xref
         </indexterm>Showing routing information</title>
       <para>When routing is enabled on a node, the tiny, small and large
       routing buffers are allocated. See <xref

-      linkend="dbdoclet.50438272_73839"/> for more details on router
+      linkend="dbdoclet.tuning_lnet_params"/> for more details on router

       buffers. This information can be shown as follows:</para>
       <screen>lnetctl routing show: show routing information
 
       buffers. This information can be shown as follows:</para>
       <screen>lnetctl routing show: show routing information
 

diff --git a/LustreProc.xml b/LustreProc.xml
index 76bc7b0..3a5f88f 100644 (file)
--- a/LustreProc.xml
+++ b/LustreProc.xml
@@ -2491,7 +2491,7 @@ nid                    refs   peer    max   tx    min
 ldlm.namespaces.myth-MDT0000-mdc-ffff8804296c2800.lru_max_age=900000
     </screen>
   </section>
 ldlm.namespaces.myth-MDT0000-mdc-ffff8804296c2800.lru_max_age=900000
     </screen>
   </section>

-  <section xml:id="dbdoclet.50438271_87260">
+  <section xml:id="dbdoclet.tuning_setting_thread_count">

     <title><indexterm>
         <primary>proc</primary>
         <secondary>thread counts</secondary>
     <title><indexterm>
         <primary>proc</primary>
         <secondary>thread counts</secondary>

diff --git a/LustreTuning.xml b/LustreTuning.xml
index f51e325..231918c 100644 (file)
--- a/LustreTuning.xml
+++ b/LustreTuning.xml
@@ -10,7 +10,7 @@
     parameters. These parameters are contained in the 
     <literal>/etc/modprobe.d/lustre.conf</literal> file.</para>
   </note>
     parameters. These parameters are contained in the 
     <literal>/etc/modprobe.d/lustre.conf</literal> file.</para>
   </note>

-  <section xml:id="dbdoclet.50438272_55226">
+  <section xml:id="dbdoclet.tuning_optimizing_service_threads">

     <title>
     <indexterm>
       <primary>tuning</primary>
     <title>
     <indexterm>
       <primary>tuning</primary>


@@ -113,7 +113,7 @@ lctl {get,set}_param {service}.thread_{min,max,started}
         </listitem>
       </itemizedlist>
       <para>For further details, see 
         </listitem>
       </itemizedlist>
       <para>For further details, see 

-      <xref linkend="dbdoclet.50438271_87260" />.</para>
+      <xref linkend="dbdoclet.tuning_setting_thread_count" />.</para>

     </section>
     <section xml:id="dbdoclet.mdstuning">
       <title>
     </section>
     <section xml:id="dbdoclet.mdstuning">
       <title>


@@ -136,7 +136,7 @@ lctl {get,set}_param {service}.thread_{min,max,started}
 </screen>
       </para>
       <para>For details, see 
 </screen>
       </para>
       <para>For details, see 

-      <xref linkend="dbdoclet.50438271_87260" />.</para>
+      <xref linkend="dbdoclet.tuning_setting_thread_count" />.</para>

       <para>The number of MDS service threads started depends on system size
       and the load on the server, and has a default maximum of 64. The
       maximum potential number of threads (<literal>MDS_MAX_THREADS</literal>)
       <para>The number of MDS service threads started depends on system size
       and the load on the server, and has a default maximum of 64. The
       maximum potential number of threads (<literal>MDS_MAX_THREADS</literal>)


@@ -204,7 +204,7 @@ options mdt mds_num_cpts=[0]</screen>
     </example>
     </para>
   </section>
     </example>
     </para>
   </section>

-  <section xml:id="dbdoclet.50438272_73839">
+  <section xml:id="dbdoclet.tuning_lnet_params">

     <title>
     <indexterm>
       <primary>LNet</primary>
     <title>
     <indexterm>
       <primary>LNet</primary>


@@ -265,7 +265,7 @@ options ksocklnd enable_irq_affinity=0
       an administrator can bind an interface to one or more CPU partitions.
       Bindings are specified as options to the LNet modules. For more
       information on specifying module options, see 
       an administrator can bind an interface to one or more CPU partitions.
       Bindings are specified as options to the LNet modules. For more
       information on specifying module options, see 

-      <xref linkend="dbdoclet.50438293_15350" /></para>
+      <xref linkend="dbdoclet.tuning_lnet_mod_params" /></para>

       <para>For example, 
       <literal>o2ib0(ib0)[0,1]</literal> will ensure that all messages for 
       <literal>o2ib0</literal> will be handled by LND threads executing on 
       <para>For example, 
       <literal>o2ib0(ib0)[0,1]</literal> will ensure that all messages for 
       <literal>o2ib0</literal> will be handled by LND threads executing on 


@@ -2059,7 +2059,7 @@ ost.OSS.ost_io.nrs_delay_pct=hp_delay_pct:5
       </itemizedlist>
     </section>
   </section>
       </itemizedlist>
     </section>
   </section>

-  <section xml:id="dbdoclet.50438272_25884">
+  <section xml:id="dbdoclet.tuning_lockless_IO">

     <title>
     <indexterm>
       <primary>tuning</primary>
     <title>
     <indexterm>
       <primary>tuning</primary>


@@ -2341,7 +2341,7 @@ ldlm.namespaces.filter-<replaceable>fsname</replaceable>-*.
           renegotiate the new maximum RPC size.</para></caution>
       </section>
   </section>
           renegotiate the new maximum RPC size.</para></caution>
       </section>
   </section>

-  <section xml:id="dbdoclet.50438272_80545">
+  <section xml:id="dbdoclet.tuning_IO_small_files">

     <title>
     <indexterm>
       <primary>tuning</primary>
     <title>
     <indexterm>
       <primary>tuning</primary>


@@ -2381,7 +2381,7 @@ ldlm.namespaces.filter-<replaceable>fsname</replaceable>-*.
       </listitem>
     </itemizedlist>
   </section>
       </listitem>
     </itemizedlist>
   </section>

-  <section xml:id="dbdoclet.50438272_45406">
+  <section xml:id="dbdoclet.write_vs_read_performance">

     <title>
     <indexterm>
       <primary>tuning</primary>
     <title>
     <indexterm>
       <primary>tuning</primary>

diff --git a/ManagingLNet.xml b/ManagingLNet.xml
index 1fbba0a..245f699 100644 (file)
--- a/ManagingLNet.xml
+++ b/ManagingLNet.xml
@@ -277,7 +277,8 @@ ents&quot;</screen>
       script, since the script only adds extra routes after the router is
       identified.  To ensure that a router is identified correctly, make sure to
       add its local NID in the routes parameter in the modprobe lustre
       script, since the script only adds extra routes after the router is
       identified.  To ensure that a router is identified correctly, make sure to
       add its local NID in the routes parameter in the modprobe lustre

-      configuration file.  See <xref linkend='dbdoclet.50438293_15350'/>.</para>
+      configuration file.
+      See <xref linkend='dbdoclet.tuning_lnet_mod_params'/>.</para>

     </section>
     <section remap="h3">
       <title><indexterm><primary>LNet</primary></indexterm><literal>lustre_routes_conversion</literal></title>
     </section>
     <section remap="h3">
       <title><indexterm><primary>LNet</primary></indexterm><literal>lustre_routes_conversion</literal></title>