diff options
author | Etienne Dechamps <[email protected]> | 2011-09-05 15:15:45 +0200 |
---|---|---|
committer | Brian Behlendorf <[email protected]> | 2012-02-07 16:23:06 -0800 |
commit | 34037afe24e0bff97cf5262f8f1a76f5e0815dc1 (patch) | |
tree | 563a33de02991aeade1393ef1c61f4b46d733474 /include/zfs_comutil.h | |
parent | b18019d2d810585185493c62e9567fa85e51692c (diff) |
Improve ZVOL queue behavior.
The Linux block device queue subsystem exposes a number of configurable
settings described in Linux block/blk-settings.c. The defaults for these
settings are tuned for hard drives, and are not optimized for ZVOLs. Proper
configuration of these options would allow upper layers (I/O scheduler) to
take better decisions about write merging and ordering.
Detailed rationale:
- max_hw_sectors is set to unlimited (UINT_MAX). zvol_write() is able to
handle writes of any size, so there's no reason to impose a limit. Let the
upper layer decide.
- max_segments and max_segment_size are set to unlimited. zvol_write() will
copy the requests' contents into a dbuf anyway, so the number and size of
the segments are irrelevant. Let the upper layer decide.
- physical_block_size and io_opt are set to the ZVOL's block size. This
has the potential to somewhat alleviate issue #361 for ZVOLs, by warning
the upper layers that writes smaller than the volume's block size will be
slow.
- The NONROT flag is set to indicate this isn't a rotational device.
Although the backing zpool might be composed of rotational devices, the
resulting ZVOL often doesn't exhibit the same behavior due to the COW
mechanisms used by ZFS. Setting this flag will prevent upper layers from
making useless decisions (such as reordering writes) based on incorrect
assumptions about the behavior of the ZVOL.
Signed-off-by: Brian Behlendorf <[email protected]>
Diffstat (limited to 'include/zfs_comutil.h')
0 files changed, 0 insertions, 0 deletions