[dm-devel] virtio_blk: fix defaults for max_hw_sectors and max_segment_size
axboe at kernel.dk
Wed Nov 26 21:53:21 UTC 2014
On 11/26/2014 02:51 PM, Mike Snitzer wrote:
> On Wed, Nov 26 2014 at 3:54pm -0500,
> Jens Axboe <axboe at kernel.dk> wrote:
>> On 11/26/2014 01:51 PM, Mike Snitzer wrote:
>>> On Wed, Nov 26 2014 at 2:48pm -0500,
>>> Jens Axboe <axboe at kernel.dk> wrote:
>>>> That code isn't even in mainline, as far as I can tell...
>>> Right, it is old RHEL6 code.
>>> But I've yet to determine what changed upstream that enables this to
>>> "just work" with a really large max_sectors (I haven't been looking
>> Kind of hard for the rest of us to say, since it's triggering a BUG in
>> code we don't have :-)
> I never asked you or others to weigh in on old RHEL6 code. Once I
> realized upstream worked even if max_sectors is _really_ high I said
> "sorry for the noise".
> But while you're here, I wouldn't mind getting your take on virtio-blk
> setting max_hw_sectors to -1U.
> As I said in my original reply to mst: it only makes sense to set a
> really high initial upper bound like that in a driver if that driver
> goes on to stack an underlying device's limit.
-1U should just work, IMHO, there's no reason we should need to cap it
at some synthetic value. That said, it seems it should be one of those
parameters that should be negotiated up and set appropriately.
More information about the dm-devel