From: Matt Ezell Date: Wed, 5 Feb 2014 04:20:30 +0000 (-0500) Subject: LUDOC-11 typos: Fix references to unknown lustre versions X-Git-Tag: 2.6.0~13 X-Git-Url: https://git.whamcloud.com/?a=commitdiff_plain;h=2a3460ef7f3e86d86b7e76e2f33cd5f483bdc24c;p=doc%2Fmanual.git LUDOC-11 typos: Fix references to unknown lustre versions Replace the character '1' with 'l' to avoid the message: unrecognised Lustre version Signed-off-by: Matt Ezell Change-Id: Icc0d71c7c73bd53bce79032ba79f97480fd2a56d Reviewed-on: http://review.whamcloud.com/9126 Tested-by: Jenkins Reviewed-by: James Nunez Reviewed-by: Richard Henwood --- diff --git a/ConfigurationFilesModuleParameters.xml b/ConfigurationFilesModuleParameters.xml index 1093a14..67d112d 100644 --- a/ConfigurationFilesModuleParameters.xml +++ b/ConfigurationFilesModuleParameters.xml @@ -176,7 +176,7 @@ routes ("") routes="[tcp,vib] 2 [8-14/2]@elan" says that 2 networks (tcp0 and vib0) are accessible through 4 routers (8@elan, 10@elan, 12@elan and 14@elan). The hopcount of 2 means that traffic to both these networks will be traversed 2 routers - first one of the routers specified in this entry, then one more. Duplicate entries, entries that route to a local network, and entries that specify routers on a non-local network are ignored. Prior to release 2.5, a conflict between equivalent entries was resolved in favor of the route with the shorter hopcount. The hopcount, if omitted, defaults to 1 (the remote network is adjacent).. - Since 2.5, equivalent entries are resolved in favor of the route with the lowest priority number or shorter hopcount if the priorities are equal. The priority, if omitted, defaults to 0. The hopcount, if omitted, defaults to 1 (the remote network is adjacent). + Since 2.5, equivalent entries are resolved in favor of the route with the lowest priority number or shorter hopcount if the priorities are equal. The priority, if omitted, defaults to 0. The hopcount, if omitted, defaults to 1 (the remote network is adjacent). It is an error to specify routes to the same destination with routers on different local networks. If the target network string contains no expansions, then the hopcount defaults to 1 and may be omitted (that is, the remote network is adjacent). In practice, this is true for most multi-network configurations. It is an error to specify an inconsistent hop count for a given target network. This is why an explicit hopcount is required if the target network string specifies more than one network. @@ -264,7 +264,7 @@ forwarding ("")
<indexterm><primary>configuring</primary><secondary>network</secondary><tertiary>rnet_htable_size</tertiary></indexterm> <literal>rnet_htable_size</literal> - rnet_htable_size is an integer that indicates how many remote networks the internal LNet hash table is configured to handle. rnet_htable_size is used for optimizing the hash table size and does not put a limit on how many remote networks you can have. The default hash table size when this parameter is not specified is: 128. + rnet_htable_size is an integer that indicates how many remote networks the internal LNet hash table is configured to handle. rnet_htable_size is used for optimizing the hash table size and does not put a limit on how many remote networks you can have. The default hash table size when this parameter is not specified is: 128.
diff --git a/ManagingLNET.xml b/ManagingLNET.xml index b668339..262b6e1 100644 --- a/ManagingLNET.xml +++ b/ManagingLNET.xml @@ -109,7 +109,7 @@ To remove all Lustre modules, run: A Lustre node always uses the same local NID to communicate with a given peer NID. The criteria used to determine the local NID are: - Lowest route priority number (lower number, higher priority). + Lowest route priority number (lower number, higher priority). Fewest hops (to minimize routing), and