[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200427170613.GA13686@lst.de>
Date: Mon, 27 Apr 2020 19:06:13 +0200
From: Christoph Hellwig <hch@....de>
To: Martijn Coenen <maco@...roid.com>
Cc: axboe@...nel.dk, hch@....de, ming.lei@...hat.com,
narayan@...gle.com, zezeozue@...gle.com, kernel-team@...roid.com,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
maco@...gle.com, bvanassche@....org, Chaitanya.Kulkarni@....com,
jaegeuk@...nel.org
Subject: Re: [PATCH v3 0/9] Add a new LOOP_SET_FD_AND_STATUS ioctl
I've just been looking over the loop driver for other reasons,
and noticed that setting the block size still isn't possible
with LOOP_SET_FD_AND_STATUS as far as I can tell. Might that
be worth it? Also maybe an explicit direct I/O flag, and maybe
enough padding with a future proof flags bitmap that we can easily
extend it for new features if they pop up?
Powered by blists - more mailing lists