summaryrefslogtreecommitdiffstats
path: root/drivers/block/rsxx
diff options
context:
space:
mode:
authorJens Axboe <axboe@fb.com>2015-07-16 17:14:26 +0200
committerJens Axboe <axboe@fb.com>2015-07-17 16:41:53 +0200
commit0034af036554c39eefd14d835a8ec3496ac46712 (patch)
tree54a9262ca37905600872eb8638d5453a82f59520 /drivers/block/rsxx
parentblock: have drivers use blk_queue_max_discard_sectors() (diff)
downloadlinux-0034af036554c39eefd14d835a8ec3496ac46712.tar.xz
linux-0034af036554c39eefd14d835a8ec3496ac46712.zip
block: make /sys/block/<dev>/queue/discard_max_bytes writeable
Lots of devices support huge discard sizes these days. Depending on how the device handles them internally, huge discards can introduce massive latencies (hundreds of msec) on the device side. We have a sysfs file, discard_max_bytes, that advertises the max hardware supported discard size. Make this writeable, and split the settings into a soft and hard limit. This can be set from 'discard_granularity' and up to the hardware limit. Add a new sysfs file, 'discard_max_hw_bytes', that shows the hw set limit. Reviewed-by: Jeff Moyer <jmoyer@redhat.com> Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'drivers/block/rsxx')
0 files changed, 0 insertions, 0 deletions