From 8621a9c816e3f512dfb2eea927e36cc461639b50 Mon Sep 17 00:00:00 2001 From: Richard Henwood Date: Tue, 30 Apr 2013 17:27:26 -0500 Subject: [PATCH] LUDOC-117 cleanup: minor changes to wording and markup. Minor changes to add clarify. Signed-off-by: Richard Henwood Change-Id: Ic5c8c6cf23d9779c0d1ad7a5cb702a179f9dca0b Reviewed-on: http://review.whamcloud.com/6218 Tested-by: Hudson Reviewed-by: Linda Bebernes --- LNETSelfTest.xml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/LNETSelfTest.xml b/LNETSelfTest.xml index ebfcc10..7c34d8f 100644 --- a/LNETSelfTest.xml +++ b/LNETSelfTest.xml @@ -55,7 +55,7 @@ LNET Self-Test Overview - Test nodes can be in either kernel or userspace. A console node can invite a kernel test node to join the session by running lst add_group NID, but the console node cannot actively add a userspace test node to the session. A console node can passively accept a test node to the session while the test node is running lstclient to connect to the console node. + Test nodes can be in either kernel or userspace. A console node can invite a kernel test node to join the session by running lst add_group NID, but the console node cannot actively add a userspace test node to the session. A console node can passively accept a test node to the session while the test node is running lstclient to connect to the console node.
Prerequisites @@ -71,7 +71,7 @@ LNET Self-Test Overview lnet_selftest - One of the klnds (i.e, ksocklnd, ko2iblnd...) as needed by your network configuration + klnds: A kernel Lustre network driver (LND) (i.e, ksocklnd, ko2iblnd...) as needed by your network configuration. To load the required modules, run: @@ -87,7 +87,7 @@ LNET Self-Test Overview 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.
Creating a Session - A session 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 . + A session 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 . 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. The following commands set the LST_SESSION environment variable to identify the session on the console node and create a session called read_write: export LST_SESSION=$$ @@ -222,7 +222,7 @@ lst end_session --force - Ends conflicting sessions. This determines who 'wins' when one session conflicts with another. For example, if there is already an active session on this node, then the attempt to create a new session fails unless the -force flag is specified. If the -force flag is specified, then the active session is ended. Similarly, if a session attempts to add a node that is already 'owned' by another session, the -force flag allows this session to 'steal' the node. + Ends conflicting sessions. This determines who 'wins' when one session conflicts with another. For example, if there is already an active session on this node, then the attempt to create a new session fails unless the --force flag is specified. If the --force flag is specified, then the active session is ended. Similarly, if a session attempts to add a node that is already 'owned' by another session, the --force flag allows this session to 'steal' the node. @@ -544,7 +544,7 @@ Client1 $ lstclient --sesid 192.168.1.52@tcp --group clients Batch and Test Commands This section describes lst batch and test commands. add_batch name - A default batch test set named batch is created when the session is started. You can specify a batch name by using add_batch: + A default batch test set named batch is created when the session is started. You can specify a batch name by using add_batch: $ lst add_batch bulkperf Creates a batch test called bulkperf. @@ -790,7 +790,7 @@ $ lst list_batch bulkperf --server --active name [--test index] [--timeout seconds] - [--loop loopcount] + [--loop loopcount] [--delay seconds] [--all] -- 1.8.3.1