On Tue, Jul 14 2015 at 11:02am -0400, Jens Axboe <[email protected]> wrote:
> 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. Looks pretty good, but we'll lose the original discard_max_bytes once it is changed. That information loss will prevent users from knowing what adjustments are possible over time. This may be OK, but figured i'd raise it. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
