From f499e19c65bfcb727e00e3bf3a674fc85c05b8fc Mon Sep 17 00:00:00 2001 From: Andreas Dilger Date: Mon, 12 Apr 2021 14:37:04 -0600 Subject: [PATCH] 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 Change-Id: Ic11a220499198c7bf3d1485d9ed62033c6ef0be3 Reviewed-on: https://review.whamcloud.com/43282 Tested-by: jenkins --- LustreProc.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/LustreProc.xml b/LustreProc.xml index 03c059b..76bc7b0 100644 --- a/LustreProc.xml +++ b/LustreProc.xml @@ -1348,7 +1348,7 @@ write RPCs in flight: 0 llite.fsname_instance.max_read_ahead_mb - - 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 read() 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 llite.fsname_instance.max_read_ahead_per_file_mb - 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 max_read_ahead_mb. -- 1.8.3.1