<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>
- <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>
</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
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>
</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>
</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>)
</example>
</para>
</section>
- <section xml:id="dbdoclet.50438272_73839">
+ <section xml:id="dbdoclet.tuning_lnet_params">
<title>
<indexterm>
<primary>LNet</primary>
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
</itemizedlist>
</section>
</section>
- <section xml:id="dbdoclet.50438272_25884">
+ <section xml:id="dbdoclet.tuning_lockless_IO">
<title>
<indexterm>
<primary>tuning</primary>
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>
</listitem>
</itemizedlist>
</section>
- <section xml:id="dbdoclet.50438272_45406">
+ <section xml:id="dbdoclet.write_vs_read_performance">
<title>
<indexterm>
<primary>tuning</primary>
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>