From: Dan Williams Date: Sat, 19 Jul 2008 00:47:13 +0000 (-0700) Subject: Documentation fixup for stripe_cache_size X-Git-Tag: mdadm-3.0-devel1~92 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=800053d6003f78e7302144bbacb4ccb488721c2e;p=thirdparty%2Fmdadm.git Documentation fixup for stripe_cache_size Signed-off-by: Dan Williams --- diff --git a/md.4 b/md.4 index ef43d9d7..f6d60fa2 100644 --- a/md.4 +++ b/md.4 @@ -526,19 +526,22 @@ Finally, "idle" can be written to stop the check/repair process. .B md/stripe_cache_size This is only available on RAID5 and RAID6. It records the size (in pages per device) of the stripe cache which is used for synchronising -all read and write operations to the array. The default is 128. +all write operations to the array and all read operations if the array +is degraded. The default is 256. Valid values are 17 to 32768. Increasing this number can increase performance in some situations, at -some cost in system memory. +some cost in system memory. Note, setting this value too high can +result in an "out of memory" condition for the system. + +memory_consumed = system_page_size * nr_disks * stripe_cache_size .TP .B md/preread_bypass_threshold This is only available on RAID5 and RAID6. This variable sets the number of times MD will service a full-stripe-write before servicing a stripe that requires some "prereading". For fairness this defaults to -1. Setting this to 0 maximizes sequential-write throughput at the cost -of fairness to threads doing small or random writes. Valid values are 0 -to stripe_cache_size. - +1. Valid values are 0 to stripe_cache_size. Setting this to 0 +maximizes sequential-write throughput at the cost of fairness to threads +doing small or random writes. .SS KERNEL PARAMETERS