<para>This section describes how to create and run an LNET self-test. The examples shown are for a test that simulates the traffic pattern of a set of Lustre servers on a TCP network accessed by Lustre clients on an InfiniBand network connected via LNET routers. In this example, half the clients are reading and half the clients are writing.</para>
<section remap="h3">
<title>23.2.1 Creating a Session</title>
- <para>A <emphasis>session</emphasis> is a set of processes that run on a test node. Only one session can be run at a time on a test node to ensure that the session has exclusive use of the node. The console node is used to create, change or destroy a session (new_session, end_session, show_session). For more about session parameters, see <xref linkend="dbdoclet.50438223_91247">Session Commands</xref>.</para>
+ <para>A <emphasis>session</emphasis> is a set of processes that run on a test node. Only one session can be run at a time on a test node to ensure that the session has exclusive use of the node. The console node is used to create, change or destroy a session (new_session, end_session, show_session). For more about session parameters, see <xref linkend="dbdoclet.50438223_91247"/>.</para>
<para>Almost all operations should be performed within the context of a session. From the console node, a user can only operate nodes in his own session. If a session ends, the session context in all test nodes is stopped.</para>
<para>The following commands set the LST_SESSION environment variable to identify the session on the console node and create a session called read_write:</para>
<screen>export LST_SESSION=$$
</section>
<section xml:id='dbdoclet.50438223_42848'>
<title>23.2.3 Defining and Running the Tests</title>
- <para>A <emphasis>test</emphasis> generates a network load between two groups of nodes, a source group identified using the <literal>--from</literal> parameter and a target group identified using the <literal>--to</literal> parameter. When a test is running, each node in the <literal>--from<emphasis><group></emphasis></literal> simulates a client by sending requests to nodes in the <literal>--to<emphasis><group></emphasis></literal>, which are simulating a set of servers, and then receives responses in return. This activity is designed to mimic Lustre RPC traffic.</para>
+ <para>A <emphasis>test</emphasis> generates a network load between two groups of nodes, a source group identified using the <literal>--from</literal> parameter and a target group identified using the <literal>--to</literal> parameter. When a test is running, each node in the <literal>--from<replaceable><group></replaceable></literal> simulates a client by sending requests to nodes in the <literal>--to<replaceable><group></replaceable></literal>, which are simulating a set of servers, and then receives responses in return. This activity is designed to mimic Lustre RPC traffic.</para>
<para>A <emphasis>batch</emphasis> is a collection of tests that are started and stopped together and run in parallel. A test must always be run as part of a batch, even if it is just a single test. Users can only run or stop a test batch, not individual tests.</para>
<para>Tests in a batch are non-destructive to the file system, and can be run in a normal Lustre environment (provided the performance impact is acceptable).</para>
- <para>A simple batch might contain a single test, for example, to determine whether the network bandwidth presents an I/O bottleneck. In this example, the <literal>--to<emphasis><group></emphasis></literal> could be comprised of Lustre OSSs and <literal>--from<emphasis><group></emphasis></literal> the compute nodes. A second test could be added to perform pings from a login node to the MDS to see how checkpointing affects the <literal>ls -l</literal> process.</para>
+ <para>A simple batch might contain a single test, for example, to determine whether the network bandwidth presents an I/O bottleneck. In this example, the <literal>--to<replaceable><group></replaceable></literal> could be comprised of Lustre OSSs and <literal>--from<replaceable><group></replaceable></literal> the compute nodes. A second test could be added to perform pings from a login node to the MDS to see how checkpointing affects the <literal>ls -l</literal> process.</para>
<para>Two types of tests are available:</para>
<itemizedlist>
<listitem>
<tbody>
<row>
<entry>
- <para><literal>--timeout<emphasis><seconds></emphasis></literal></para>
+ <para><literal>--timeout<replaceable><seconds></replaceable></literal></para>
</entry>
<entry>
<para>Console timeout value of the session. The session ends automatically if it remains idle (i.e., no commands are issued) for this period.</para>
<para><emphasis role="bold">Example:</emphasis></para>
<screen>$ lst new_session --force read_write</screen>
<para><literal>
- <emphasis role="bold">end_session</emphasis>
+ <replaceable role="bold">end_session</replaceable>
</literal></para>
<para>Stops all operations and tests in the current session and clears the session's status.</para>
<screen>$ lst end_session</screen>
<para><literal>
- <emphasis role="bold">show_session</emphasis>
+ <replaceable role="bold">show_session</replaceable>
</literal></para>
<para>Shows the session information. This command prints information about the current session. It does not require LST_SESSION to be defined in the process environment.</para>
<screen>$ lst show_session</screen>
<title>23.3.2 Group Commands</title>
<para>This section describes <literal>lst</literal> group commands.</para>
<para><literal>
- <emphasis role="bold">add_group</emphasis>
- <emphasis> <name> <NIDS> [<NIDs>...]</emphasis>
+ <replaceable role="bold">add_group</replaceable>
+ <replaceable> <name> <NIDS> [<NIDs>...]</replaceable>
</literal></para>
<para>Creates the group and adds a list of test nodes to the group.</para>
<informaltable frame="all">
<row>
<entry>
<para> <literal>
- <emphasis><name></emphasis>
+ <replaceable><name></replaceable>
</literal></para>
</entry>
<entry>
<row>
<entry>
<para> <literal>
- <emphasis><NIDs></emphasis>
+ <replaceable><NIDs></replaceable>
</literal></para>
</entry>
<entry>
<para><emphasis role="bold">Example:</emphasis></para>
<screen>$ lst add_group servers 192.168.10.[35,40-45]@tcp$ lst add_group clients 192.168.1.[10-100]@tcp 192.168.[2,4].\[10-20]@tcp</screen>
<para><literal>
- <emphasis role="bold">update_group</emphasis>
- <emphasis><name></emphasis>
- <emphasis role="bold">[--refresh] [--clean</emphasis>
- <emphasis><status></emphasis>
- <emphasis role="bold">] [--remove</emphasis>
- <emphasis><NIDs></emphasis>
- <emphasis role="bold">]</emphasis>
+ <replaceable role="bold">update_group</replaceable>
+ <replaceable><name></replaceable>
+ <replaceable role="bold">[--refresh] [--clean</replaceable>
+ <replaceable><status></replaceable>
+ <replaceable role="bold">] [--remove</replaceable>
+ <replaceable><NIDs></replaceable>
+ <replaceable role="bold">]</replaceable>
</literal></para>
<para>Updates the state of nodes in a group or adjusts a group's membership. This command is useful if some nodes have crashed and should be excluded from the group.</para>
<informaltable frame="all">
<tbody>
<row>
<entry>
+ <para>
<literal>
- <para>--refresh</para>
+ --refresh
</literal>
+ </para>
</entry>
<entry nameend="c3" namest="c2">
<para> Refreshes the state of all inactive nodes in the group.</para>
</row>
<row>
<entry>
- <para> <literal>--clean<emphasis><status></emphasis></literal></para>
+ <para> <literal>--clean<replaceable><status></replaceable></literal></para>
</entry>
<entry nameend="c3" namest="c2">
<para> Removes nodes with a specified status from the group. Status may be:</para>
</row>
<row>
<entry>
- <para> <literal>--remove<emphasis><NIDs></emphasis></literal></para>
+ <para> <literal>--remove<replaceable><NIDs></replaceable></literal></para>
</entry>
<entry nameend="c3" namest="c2">
<para> Removes specified nodes from the group.</para>
invalid == busy || down || unknown
$ lst update_group clients --remove \192.168.1.[10-20]@tcp</screen>
<para><literal>
- <emphasis role="bold">list_group [</emphasis>
- <emphasis><name></emphasis>
- <emphasis role="bold">] [--active] [--busy] [--down] [--unknown] [--all]</emphasis>
+ <replaceable role="bold">list_group [</replaceable>
+ <replaceable><name></replaceable>
+ <replaceable role="bold">] [--active] [--busy] [--down] [--unknown] [--all]</replaceable>
</literal></para>
<para>Prints information about a group or lists all groups in the current session if no group is specified.</para>
<informaltable frame="all">
<row>
<entry>
<para><literal>
- <emphasis><name></emphasis>
+ <replaceable><name></replaceable>
</literal></para>
</entry>
<entry>
</row>
<row>
<entry>
+ <para>
<literal>
- <para>--active</para>
+ --active
</literal>
+ </para>
</entry>
<entry>
<para> Lists the active nodes.</para>
</row>
<row>
<entry>
+ <para>
<literal>
- <para>--busy</para>
+ --busy
</literal>
+ </para>
</entry>
<entry>
<para> Lists the busy nodes.</para>
<row>
<entry>
<literal>
- <para>--down</para>
+ --down
</literal>
</entry>
<entry>
<row>
<entry>
<literal>
- <para>--unknown</para>
+ --unknown
</literal>
</entry>
<entry>
<row>
<entry>
<literal>
- <para>--all</para>
+ --all
</literal>
</entry>
<entry>
192.168.1.12@tcp Busy
Total 1 node</screen>
<para><literal>
- <emphasis role="bold">del_group</emphasis>
- <emphasis> <name></emphasis>
+ <replaceable role="bold">del_group</replaceable>
+ <replaceable> <name></replaceable>
</literal></para>
<para>Removes a group from the session. If the group is referred to by any test, then the operation fails. If nodes in the group are referred to only by this group, then they are kicked out from the current session; otherwise, they are still in the current session.</para>
<screen>$ lst del_group clients</screen>
- <para><literal><emphasis role="bold">lstclient --sesid</emphasis><emphasis> <NID> </emphasis><emphasis role="bold">--group</emphasis><emphasis> <name></emphasis> [--server_mode]</literal></para>
+ <para><literal><replaceable role="bold">lstclient --sesid</replaceable><replaceable> <NID> </replaceable><replaceable role="bold">--group</replaceable><replaceable> <name></replaceable> [--server_mode]</literal></para>
<para>Use <literal>lstclient</literal> to run the userland self-test client. The <literal>lstclient</literal> command should be executed after creating a session on the console. There are only two mandatory options for <literal>lstclient</literal>:</para>
<informaltable frame="all">
<tgroup cols="2">
<row>
<entry>
<literal>
- <para> --sesid<emphasis><NID></emphasis></para>
+ --sesid<replaceable><NID></replaceable>
</literal>
</entry>
<entry>
<row>
<entry>
<literal>
- <para> --group<emphasis><name></emphasis></para>
+ --group<replaceable><name></replaceable>
</literal>
</entry>
<entry>
<row>
<entry>
<literal>
- <para> --server_mode</para>
+ --server_mode
</literal>
</entry>
<entry>
<title>23.3.3 Batch and Test Commands</title>
<para>This section describes <literal>lst</literal> batch and test commands.</para>
<para><literal>
- <emphasis role="bold">add_batch NAME</emphasis>
+ <replaceable role="bold">add_batch NAME</replaceable>
</literal></para>
<para>A default batch test set named batch is created when the session is started. You can specify a batch name by using add_batch:</para>
<screen>$ lst add_batch bulkperf</screen>
<para>Creates a batch test called <literal>bulkperf</literal>.</para>
- <para><literal>
- <emphasis role="bold">add_test --batch <emphasis><<emphasis role="italic">batchname</emphasis>></emphasis> [--loop<#>] <emphasis role="bold">[--concurrency</emphasis><emphasis><#></emphasis><emphasis role="bold">] [--distribute</emphasis><emphasis><#:#></emphasis><emphasis role="bold">]</emphasis><para>--from<emphasis> <<emphasis role="italic">group</emphasis>></emphasis> --to <emphasis><<emphasis role="italic">group</emphasis>></emphasis> {brw|ping} <test options></para></emphasis>
- </literal></para>
+ <screen>
+ <replaceable role="bold">add_test --batch <replaceable><<replaceable role="italic">batchname</replaceable>></replaceable> [--loop<#>] <replaceable role="bold">[--concurrency</replaceable><replaceable><#></replaceable><replaceable role="bold">] [--distribute</replaceable><replaceable><#:#></replaceable><replaceable role="bold">]</replaceable> \
+--from<replaceable> <<replaceable role="italic">group</replaceable>></replaceable> --to <replaceable><<replaceable role="italic">group</replaceable>></replaceable> {brw|ping} <test options></replaceable>
+ </screen>
<para>Adds a test to a batch. The parameters are described below.</para>
<informaltable frame="all">
<tgroup cols="3">
<tbody>
<row>
<entry>
- <para> <literal>--batch<emphasis><batchname></emphasis></literal></para>
+ <para> <literal>--batch<replaceable><batchname></replaceable></literal></para>
</entry>
<entry nameend="c3" namest="c2">
<para>Names a group of tests for later execution.</para>
<row>
<entry>
<literal>
- <para> --loop<emphasis><#></emphasis></para>
+ --loop<replaceable><#></replaceable>
</literal>
</entry>
<entry nameend="c3" namest="c2">
<row>
<entry>
<literal>
- <para> --concurrency<emphasis><#></emphasis></para>
+ --concurrency<replaceable><#></replaceable>
</literal>
</entry>
<entry nameend="c3" namest="c2">
<row>
<entry>
<literal>
- <para> --distribute<emphasis><#:#></emphasis></para>
+ --distribute<replaceable><#:#></replaceable>
</literal>
</entry>
<entry nameend="c3" namest="c2">
<row>
<entry>
<literal>
- <para>--from<emphasis><group></emphasis></para>
+ --from<replaceable><group></replaceable>
</literal>
</entry>
<entry nameend="c3" namest="c2">
<row>
<entry>
<literal>
- <para>--to<emphasis><group></emphasis></para>
+ --to<replaceable><group></replaceable>
</literal>
</entry>
<entry nameend="c3" namest="c2">
</row>
<row>
<entry>
- <para><literal>ping</literal></para>
+ <literal>ping</literal>
</entry>
<entry nameend="c3" namest="c2">
- <para>Sends a small request message, resulting in a small reply message. For more details, see <xref linkend="dbdoclet.50438223_42848">Defining and Running the Tests</xref></para>
+ <para>Sends a small request message, resulting in a small reply message. For more details, see <xref linkend="dbdoclet.50438223_42848"/></para>
</entry>
</row>
<row>
<entry>
- <para><literal>brw</literal></para>
+ <literal>brw</literal>
</entry>
<entry nameend="c3" namest="c2">
- <para>Sends a small request message followed by a bulk data transfer, resulting in a small reply message. <xref linkend="dbdoclet.50438223_42848">Defining and Running the Tests</xref>. Options are:</para>
+ <para>Sends a small request message followed by a bulk data transfer, resulting in a small reply message. <xref linkend="dbdoclet.50438223_42848"/>. Options are:</para>
</entry>
</row>
<row>
</entry>
<entry>
<literal>
- <para>read | write</para>
+ read | write
</literal>
</entry>
<entry>
</row>
<row>
<entry>
- <para> </para>
</entry>
<entry>
<literal>
- <para>size=<#>| <#>K | <#>M</para>
+ size=<#>| <#>K | <#>M
</literal>
</entry>
<entry>
</row>
<row>
<entry>
- <para> </para>
</entry>
<entry>
<literal>
- <para>check=full|simple</para>
+ check=full|simple
</literal>
</entry>
<entry>
--distribute 4:2 (C1,C2,C3,C4->S1,S2), (C5, C6->S3, S1)
--distribute 6:3 (C1,C2,C3,C4,C5,C6->S1,S2,S3)</screen>
<para>The setting <literal>--distribute 1:1</literal> is the default setting where each source node communicates with one target node.</para>
- <para>When the setting <literal>--distribute 1:<emphasis><n></emphasis></literal> (where <emphasis>
- <literal><n></literal>
- </emphasis> is the size of the target group) is used, each source node communicates with every node in the target group.</para>
+ <para>When the setting <literal>--distribute 1:<replaceable><n></replaceable></literal> (where <literal><replaceable><n></replaceable></literal> is the size of the target group) is used, each source node communicates with every node in the target group.</para>
<para>Note that if there are more source nodes than target nodes, some source nodes may share the same target nodes. Also, if there are more target nodes than source nodes, some higher-ranked target nodes will be idle.</para>
<para><emphasis role="bold">Example showing a <literal>brw</literal> test:</emphasis></para>
<screen>$ lst add_group clients 192.168.1.[10-17]@tcp
</listitem>
</itemizedlist>
<para><emphasis role="bold">
- <literal><emphasis role="bold">list_batch [</emphasis><emphasis><emphasis role="italic"><name</emphasis>></emphasis><emphasis role="bold">] [--test</emphasis><emphasis> <<emphasis role="italic">index</emphasis>></emphasis><emphasis role="bold">] [--active] [--invalid]</emphasis> [--server | client<emphasis role="bold">]</emphasis></literal>
+ <literal><replaceable role="bold">list_batch [</replaceable><replaceable><replaceable role="italic"><name</replaceable>></replaceable><replaceable role="bold">] [--test</replaceable><replaceable> <<replaceable role="italic">index</replaceable>></replaceable><replaceable role="bold">] [--active] [--invalid]</replaceable> [--server | client<replaceable role="bold">]</replaceable></literal>
</emphasis></para>
<para>Lists batches in the current session or lists client and server nodes in a batch or a test.</para>
<informaltable frame="all">
<row>
<entry>
<literal>
- <para>--test<emphasis><index></emphasis></para>
+ --test<replaceable><index></replaceable>
</literal>
</entry>
<entry nameend="c3" namest="c2">
</entry>
<entry>
<literal>
- <para>server | client</para>
+ server | client
</literal>
</entry>
<entry>
192.168.10.102@tcp Active
192.168.10.103@tcp Active</screen>
<para><literal>
- <emphasis role="bold">run</emphasis>
- <emphasis role="bold">
- <emphasis> <<emphasis role="italic">name</emphasis>></emphasis>
- </emphasis>
+ <replaceable role="bold">run</replaceable>
+ <replaceable role="bold">
+ <replaceable> <<replaceable role="italic">name</replaceable>></replaceable>
+ </replaceable>
</literal></para>
<para>Runs the batch.</para>
<screen>$ lst run bulkperf</screen>
<para><literal>
- <emphasis role="bold">
- <emphasis role="bold">stop </emphasis>
- <emphasis><<emphasis role="italic">name</emphasis>></emphasis>
- </emphasis>
+ <replaceable role="bold">
+ <replaceable role="bold">stop </replaceable>
+ <replaceable><<replaceable role="italic">name</replaceable>></replaceable>
+ </replaceable>
</literal></para>
<para>Stops the batch.</para>
<screen>$ lst stop bulkperf</screen>
<para><emphasis role="bold">
<literal>
- <emphasis role="bold">query </emphasis>
- <emphasis><<emphasis role="italic">name</emphasis>> </emphasis>
- <emphasis role="bold">[--test</emphasis>
- <emphasis> <<emphasis role="italic">index</emphasis>></emphasis>
- <emphasis role="bold">] [--timeout</emphasis>
- <emphasis> <<emphasis role="italic">seconds</emphasis>></emphasis>
- <emphasis role="bold">] [--loop</emphasis>
- <emphasis><#></emphasis>
- <emphasis role="bold">] [--delay</emphasis>
- <emphasis><<emphasis role="italic">seconds</emphasis>></emphasis>
- <emphasis role="bold">] [--all]</emphasis>
+ <replaceable role="bold">query </replaceable>
+ <replaceable><<replaceable role="italic">name</replaceable>> </replaceable>
+ <replaceable role="bold">[--test</replaceable>
+ <replaceable> <<replaceable role="italic">index</replaceable>></replaceable>
+ <replaceable role="bold">] [--timeout</replaceable>
+ <replaceable> <<replaceable role="italic">seconds</replaceable>></replaceable>
+ <replaceable role="bold">] [--loop</replaceable>
+ <replaceable><#></replaceable>
+ <replaceable role="bold">] [--delay</replaceable>
+ <replaceable><<replaceable role="italic">seconds</replaceable>></replaceable>
+ <replaceable role="bold">] [--all]</replaceable>
</literal>
</emphasis></para>
<para>Queries the batch status.</para>
<row>
<entry>
<literal>
- <para>--test<emphasis><index></emphasis></para>
+ --test<replaceable><index></replaceable>
</literal>
</entry>
<entry>
<row>
<entry>
<literal>
- <para>--timeout<emphasis><seconds></emphasis></para>
+ --timeout<replaceable><seconds></replaceable>
</literal>
</entry>
<entry>
<row>
<entry>
<literal>
- <para>--loop<emphasis><#></emphasis></para>
+ --loop<replaceable><#></replaceable>
</literal>
</entry>
<entry>
<row>
<entry>
<literal>
- <para>--delay<emphasis><seconds></emphasis></para>
+ --delay<replaceable><seconds></replaceable>
</literal>
</entry>
<entry>
<row>
<entry>
<literal>
- <para>--all</para>
+ --all
</literal>
</entry>
<entry>
<title>23.3.4 Other Commands</title>
<para>This section describes other <literal>lst</literal> commands.</para>
<para><literal>
- <emphasis role="bold">
- <emphasis role="bold">ping [-session] [--group</emphasis>
- <emphasis><<emphasis role="italic">name</emphasis>></emphasis>
- <emphasis role="bold">] [--nodes</emphasis>
- <emphasis> <NIDs></emphasis>
- <emphasis role="bold">] [--batch</emphasis>
- <emphasis> <<emphasis role="italic">name</emphasis>></emphasis>
- <emphasis role="bold">] [--server] [--timeout</emphasis>
- <emphasis> <<emphasis role="italic">seconds</emphasis>></emphasis>
- <emphasis role="bold">]</emphasis>
- </emphasis>
+ <replaceable role="bold">
+ <replaceable role="bold">ping [-session] [--group</replaceable>
+ <replaceable><<replaceable role="italic">name</replaceable>></replaceable>
+ <replaceable role="bold">] [--nodes</replaceable>
+ <replaceable> <NIDs></replaceable>
+ <replaceable role="bold">] [--batch</replaceable>
+ <replaceable> <<replaceable role="italic">name</replaceable>></replaceable>
+ <replaceable role="bold">] [--server] [--timeout</replaceable>
+ <replaceable> <<replaceable role="italic">seconds</replaceable>></replaceable>
+ <replaceable role="bold">]</replaceable>
+ </replaceable>
</literal></para>
<para>Sends a 'hello' query to the nodes.</para>
<informaltable frame="all">
<row>
<entry>
<literal>
- <para>--session</para>
+ --session
</literal>
</entry>
<entry>
<row>
<entry>
<literal>
- <para>--group<emphasis><name></emphasis></para>
+ --group<replaceable><name></replaceable>
</literal>
</entry>
<entry>
<row>
<entry>
<literal>
- <para>--nodes<emphasis><NIDs></emphasis></para>
+ --nodes<replaceable><NIDs></replaceable>
</literal>
</entry>
<entry>
<row>
<entry>
<literal>
- <para>--batch<emphasis><name></emphasis></para>
+ --batch<replaceable><name></replaceable>
</literal>
</entry>
<entry>
<row>
<entry>
<literal>
- <para>--server</para>
+ --server
</literal>
</entry>
<entry>
- <para>Sends RPC to all server nodes instead of client nodes. This option is only used with <literal>--batch<emphasis><name></emphasis></literal>.</para>
+ <para>Sends RPC to all server nodes instead of client nodes. This option is only used with <literal>--batch<replaceable><name></replaceable></literal>.</para>
</entry>
</row>
<row>
<entry>
<literal>
- <para>--timeout<emphasis><seconds></emphasis></para>
+ --timeout<replaceable><seconds></replaceable>
</literal>
</entry>
<entry>
192.168.1.19@tcp Down [session: <NULL> id: LNET_NID_ANY]
192.168.1.20@tcp Down [session: <NULL> id: LNET_NID_ANY]</screen>
<para><literal>
- <emphasis role="bold">
- <emphasis role="bold">stat [--bw] [--rate] [--read] [--write] [--max] [--min] [--avg] " " [--timeout</emphasis>
- <emphasis> <<emphasis role="italic">seconds</emphasis>></emphasis>
- <emphasis role="bold">] [--delay </emphasis>
- <emphasis><<emphasis role="italic">seconds</emphasis>></emphasis>
- <emphasis role="bold">] </emphasis>
- <emphasis><<emphasis role="italic">group</emphasis>></emphasis>
- <emphasis role="bold">|<</emphasis>
- <emphasis><emphasis role="italic">NIDs</emphasis>> </emphasis>
- <emphasis role="bold">[</emphasis>
- <emphasis><<emphasis role="italic">group</emphasis>></emphasis>
- <emphasis role="bold">|</emphasis>
- <emphasis><<emphasis role="italic">NIDs</emphasis>></emphasis>
- <emphasis role="bold">]</emphasis>
- </emphasis>
+ <replaceable role="bold">
+ <replaceable role="bold">stat [--bw] [--rate] [--read] [--write] [--max] [--min] [--avg] " " [--timeout</replaceable>
+ <replaceable> <<replaceable role="italic">seconds</replaceable>></replaceable>
+ <replaceable role="bold">] [--delay </replaceable>
+ <replaceable><<replaceable role="italic">seconds</replaceable>></replaceable>
+ <replaceable role="bold">] </replaceable>
+ <replaceable><<replaceable role="italic">group</replaceable>></replaceable>
+ <replaceable role="bold">|<</replaceable>
+ <replaceable><replaceable role="italic">NIDs</replaceable>> </replaceable>
+ <replaceable role="bold">[</replaceable>
+ <replaceable><<replaceable role="italic">group</replaceable>></replaceable>
+ <replaceable role="bold">|</replaceable>
+ <replaceable><<replaceable role="italic">NIDs</replaceable>></replaceable>
+ <replaceable role="bold">]</replaceable>
+ </replaceable>
</literal></para>
<para>The collection performance and RPC statistics of one or more nodes.</para>
<informaltable frame="all">
<row>
<entry>
<literal>
- <para>--bw</para>
+ --bw
</literal>
</entry>
<entry>
<row>
<entry>
<literal>
- <para>--rate</para>
+ --rate
</literal>
</entry>
<entry>
<row>
<entry>
<literal>
- <para>--read</para>
+ --read
</literal>
</entry>
<entry>
<row>
<entry>
<literal>
- <para>--write</para>
+ --write
</literal>
</entry>
<entry>
<row>
<entry>
<literal>
- <para>--max</para>
+ --max
</literal>
</entry>
<entry>
<row>
<entry>
<literal>
- <para>--min</para>
+ --min
</literal>
</entry>
<entry>
<row>
<entry>
<literal>
- <para>--avg</para>
+ --avg
</literal>
</entry>
<entry>
<row>
<entry>
<literal>
- <para>--timeout<emphasis><seconds></emphasis></para>
+ --timeout<replaceable><seconds></replaceable>
</literal>
</entry>
<entry>
<row>
<entry>
<literal>
- <para>--delay<emphasis><seconds></emphasis></para>
+ --delay<replaceable><seconds></replaceable>
</literal>
</entry>
<entry>
<para>Only LNET performance statistics are available. By default, all statistics
information is displayed. Users can specify additional information with these options.</para>
<para><literal>
- <emphasis role="bold">show_error [--session] [<group>|<NIDs>]...</emphasis>
+ <replaceable role="bold">show_error [--session] [<group>|<NIDs>]...</replaceable>
</literal></para>
<para>Lists the number of failed RPCs on test nodes.</para>
<informaltable frame="all">
<row>
<entry>
<literal>
- <para>--session</para>
+ --session
</literal>
</entry>
<entry>
git://git.whamcloud.com / doc / manual.git / blobdiff