diff options
author | ru <ru@FreeBSD.org> | 2000-11-14 11:20:58 +0000 |
---|---|---|
committer | ru <ru@FreeBSD.org> | 2000-11-14 11:20:58 +0000 |
commit | 7d99729431353c50207fda8b9ab30e1c354c6061 (patch) | |
tree | 8d8c39d3231f9a7b91446e46dfc9b54f9eb84725 /sbin/vinum | |
parent | 56cb617a9d071d8ad21ab908ea9224e718dae618 (diff) | |
download | FreeBSD-src-7d99729431353c50207fda8b9ab30e1c354c6061.zip FreeBSD-src-7d99729431353c50207fda8b9ab30e1c354c6061.tar.gz |
Use Fx macro wherever possible.
Diffstat (limited to 'sbin/vinum')
-rw-r--r-- | sbin/vinum/vinum.8 | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/sbin/vinum/vinum.8 b/sbin/vinum/vinum.8 index 87d008d..09e5714 100644 --- a/sbin/vinum/vinum.8 +++ b/sbin/vinum/vinum.8 @@ -2306,14 +2306,18 @@ performance. In particular, most systems use far too small a stripe size. The following discussion applies to all RAID systems, not just to .Nm vinum . .Pp -The FreeBSD block I/O system issues requests of between .5kB and 60 kB; a +The +.Fx +block I/O system issues requests of between .5kB and 60 kB; a typical mix is somewhere round 8 kB. You can't stop any striping system from breaking a request into two physical requests, and if you do it wrong it can be broken into several. This will result in a significant drop in performance: the decrease in transfer time per disk is offset by the order of magnitude greater increase in latency. .Pp -With modern disk sizes and the FreeBSD I/O system, you can expect to have a +With modern disk sizes and the +.Fx +I/O system, you can expect to have a reasonably small number of fragmented requests with a stripe size between 256 kB and 512 kB; with correct RAID implementations there is no obvious reason not to increase the size to 2 or 4 MB on a large disk. |