Re: [PATCH] mm: don't cap request size based on read-ahead setting

From: Jens Axboe
Date: Mon Nov 21 2016 - 08:13:21 EST

On 11/20/2016 09:44 PM, Hillf Danton wrote:
On Saturday, November 19, 2016 3:41 AM Jens Axboe wrote:
We ran into a funky issue, where someone doing 256K buffered reads saw
128K requests at the device level. Turns out it is read-ahead capping
the request size, since we use 128K as the default setting. This doesn't
make a lot of sense - if someone is issuing 256K reads, they should see
256K reads, regardless of the read-ahead setting, if the underlying
device can support a 256K read in a single command.

Is it also making any sense to see 4M reads to meet 4M requests if
the underlying device can support 4M IO?

Depends on the device, but yes. Big raid set? You definitely want larger
requests. Which is why we have the distinction between max hardware and
kernel IO size.

By default we limit the soft IO size to 1280k for a block device. See

commit d2be537c3ba3568acd79cd178327b842e60d035e
Author: Jeff Moyer <jmoyer@xxxxxxxxxx>
Date: Thu Aug 13 14:57:57 2015 -0400

block: bump BLK_DEF_MAX_SECTORS to 2560

Jens Axboe