summaryrefslogtreecommitdiffstats
path: root/man
diff options
context:
space:
mode:
authorEtienne Dechamps <[email protected]>2015-05-10 16:40:20 +0100
committerBrian Behlendorf <[email protected]>2015-06-22 14:19:38 -0700
commit99b14de42104021f6b7d88118db010d8246bc0c0 (patch)
tree1817cf665c5daed60392277102efd679d2b66f36 /man
parente8fe6684a5128427e6ad1e75eb548b9fd0c482aa (diff)
Make metaslab_aliquot a module parameter.
This seems generally useful. metaslab_aliquot is the ZFS allocation granularity, which is roughly equivalent to what is called the stripe size in traditional RAID arrays. It seems relevant to performance tuning. Signed-off-by: Etienne Dechamps <[email protected]> Signed-off-by: Brian Behlendorf <[email protected]>
Diffstat (limited to 'man')
-rw-r--r--man/man5/zfs-module-parameters.514
1 files changed, 14 insertions, 0 deletions
diff --git a/man/man5/zfs-module-parameters.5 b/man/man5/zfs-module-parameters.5
index 250adc9ef..14c7fb81a 100644
--- a/man/man5/zfs-module-parameters.5
+++ b/man/man5/zfs-module-parameters.5
@@ -137,6 +137,20 @@ Default value: \fB8,388,608\fR.
.sp
.ne 2
.na
+\fBmetaslab_aliquot\fR (ulong)
+.ad
+.RS 12n
+Metaslab granularity, in bytes. This is roughly similar to what would be
+referred to as the "stripe size" in traditional RAID arrays. In normal
+operation, ZFS will try to write this amount of data to a top-level vdev
+before moving on to the next one.
+.sp
+Default value: \fB524,288\fR.
+.RE
+
+.sp
+.ne 2
+.na
\fBmetaslab_bias_enabled\fR (int)
.ad
.RS 12n