LUDOC-256 typo: fixed typos with mod config.

[doc/manual.git] / LustreTuning.xml

diff --git a/LustreTuning.xml b/LustreTuning.xml
index c508397..76a7f7d 100644 (file)
--- a/LustreTuning.xml
+++ b/LustreTuning.xml
@@ -57,7 +57,7 @@ xml:id="lustretuning">
     number of seeks and the OST threads just waiting for I/O. In this
     situation, it may be advisable to decrease the load by decreasing the
     number of OST threads.</para>
-    <para>Determining the optimum number of OST threads is a process of trial
+    <para>Determining the optimum number of OSS threads is a process of trial
     and error, and varies for each particular configuration. Variables include
     the number of OSTs on each OSS, number and speed of disks, RAID
     configuration, and available RAM. You may want to start with a number of
@@ -94,9 +94,9 @@ options ost oss_num_threads={N}
 lctl {get,set}_param {service}.thread_{min,max,started}
 </screen>
       </para>
-      <para>Lustre software release 2.3 introduced binding service threads to
-      CPU partition. This works in a similar fashion to binding of threads on
-      MDS. MDS thread tuning is covered in 
+         <para condition='l23'>Lustre software release 2.3 introduced binding
+      service threads to CPU partition. This works in a similar fashion to 
+      binding of threads on MDS. MDS thread tuning is covered in 
       <xref linkend="dbdoclet.mdsbinding" />.</para>
       <itemizedlist>
         <listitem>
@@ -192,7 +192,7 @@ lctl {get,set}_param {service}.thread_{min,max,started}
         <literal>mds_num_cpts=[EXPRESSION]</literal> binds the default MDS
         service threads to CPTs defined by 
         <literal>EXPRESSION</literal>. For example 
-        <literal>mdt_num_cpts=[0-3]</literal> will bind the MDS service threads
+        <literal>mds_num_cpts=[0-3]</literal> will bind the MDS service threads
         to 
         <literal>CPT[0,1,2,3]</literal>.</para>
       </listitem>
@@ -202,7 +202,7 @@ lctl {get,set}_param {service}.thread_{min,max,started}
         service threads to CPTs defined by 
         <literal>EXPRESSION</literal>. The read page service handles file close
         and readdir requests. For example 
-        <literal>mdt_rdpg_num_cpts=[4]</literal> will bind the read page threads
+        <literal>mds_rdpg_num_cpts=[4]</literal> will bind the read page threads
         to 
         <literal>CPT4</literal>.</para>
       </listitem>
@@ -213,6 +213,13 @@ lctl {get,set}_param {service}.thread_{min,max,started}
         <literal>EXPRESSION</literal>.</para>
       </listitem>
     </itemizedlist>
+       <para>Parameters must be set before module load in the file 
+    <literal>/etc/modprobe.d/lustre.conf</literal>. For example:
+    <example><title>lustre.conf</title>
+    <screen>options lnet networks=tcp0(eth0)
+options mdt mds_num_cpts=[0]</screen>
+    </example>
+    </para>
   </section>
   <section xml:id="dbdoclet.50438272_73839">
     <title>
@@ -560,7 +567,7 @@ lnet large_router_buffers=8192
         </listitem>
       </itemizedlist>
       <para>The current configuration of the CPU partition can be read from 
-      <literal>/proc/sys/lnet/cpu_partitions</literal></para>
+      <literal>/proc/sys/lnet/cpu_partition_table</literal></para>
     </section>
   </section>
   <section xml:id="dbdoclet.lndtuning">