LUDOC-11 proc: minor clarification of readahead params

Improve wording for max_read_ahead_mb and max_read_ahead_per_file_mb
to make it clear what each one is applied to.

Signed-off-by: Andreas Dilger <adilger@whamcloud.com>
Change-Id: Ic11a220499198c7bf3d1485d9ed62033c6ef0be3
Reviewed-on: https://review.whamcloud.com/43282
Tested-by: jenkins <devops@whamcloud.com>

diff --git a/LustreProc.xml b/LustreProc.xml
index 03c059b..76bc7b0 100644 (file)
--- a/LustreProc.xml
+++ b/LustreProc.xml
@@ -1348,7 +1348,7 @@ write RPCs in flight: 0
         <itemizedlist>
           <listitem>
             <para><literal>llite.<replaceable>fsname_instance</replaceable>.max_read_ahead_mb</literal>
-              - Controls the maximum amount of data readahead on a file.
+              - Controls the maximum amount of data readahead on all files.
               Files are read ahead in RPC-sized chunks (4 MiB, or the size of
               the <literal>read()</literal> call, if larger) after the second
               sequential read on a file descriptor. Random reads are done at
@@ -1367,7 +1367,7 @@ write RPCs in flight: 0
             <para><literal>llite.<replaceable>fsname_instance</replaceable>.max_read_ahead_per_file_mb</literal>
               - Controls the maximum number of megabytes (MiB) of data that
               should be prefetched by the client when sequential reads are
-              detected on a file.  This is the per-file readahead limit and
+              detected on one file.  This is the per-file readahead limit and
               cannot be larger than <literal>max_read_ahead_mb</literal>.
             </para>
           </listitem>