[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YkMabVKr+7Mg53E1@infradead.org>
Date: Tue, 29 Mar 2022 07:40:45 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Jens Axboe <axboe@...nel.dk>
Cc: Christoph Hellwig <hch@...radead.org>,
Yu Kuai <yukuai3@...wei.com>,
andriy.shevchenko@...ux.intel.com, john.garry@...wei.com,
ming.lei@...hat.com, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, yi.zhang@...wei.com
Subject: Re: [PATCH -next RFC 2/6] block: refactor to split bio thoroughly
On Tue, Mar 29, 2022 at 08:35:29AM -0600, Jens Axboe wrote:
> > But more importantly why does your use case even have splits that get
> > submitted together? Is this a case of Linus' stupidly low default
> > max_sectors when the hardware supports more, or is the hardware limited
> > to a low number of sectors per request? Or do we hit another reason
> > for the split?
>
> See the posted use case, it's running 512kb ios on a 128kb device.
That is an awfully low limit these days. I'm really not sure we should
optimize the block layer for that.
Powered by blists - more mailing lists