[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fe0b7bf9-07b1-9025-f9d6-7ace03c89a1f@kernel.dk>
Date: Thu, 21 May 2020 08:21:01 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Martijn Coenen <maco@...roid.com>, hch@....de, ming.lei@...hat.com
Cc: narayan@...gle.com, zezeozue@...gle.com, maco@...gle.com,
kernel-team@...roid.com, bvanassche@....org,
Chaitanya.Kulkarni@....com, jaegeuk@...nel.org,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 00/11] Add a new LOOP_CONFIGURE ioctl
On 5/13/20 7:38 AM, Martijn Coenen wrote:
> This series introduces a new ioctl that makes it possible to atomically
> configure a loop device. Previously, if you wanted to set parameters
> such as the offset on a loop device, this required calling LOOP_SET_FD
> to set the backing file, and then LOOP_SET_STATUS to set the offset.
> However, in between these two calls, the loop device is available and
> would accept requests, which is generally not desirable. Similar issues
> exist around setting the block size (LOOP_SET_BLOCK_SIZE) and requesting
> direct I/O mode (LOOP_SET_DIRECT_IO).
>
> There are also performance benefits with combining these ioctls into
> one, which are described in more detail in the last change in the
> series.
Thanks, applied for 5.8.
--
Jens Axboe
Powered by blists - more mailing lists