Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [PATCH v5 00/11] Add a new LOOP_CONFIGURE ioctl
To:     Martijn Coenen <maco@android.com>, hch@lst.de, ming.lei@redhat.com
Cc:     narayan@google.com, zezeozue@google.com, maco@google.com,
        kernel-team@android.com, bvanassche@acm.org,
        Chaitanya.Kulkarni@wdc.com, jaegeuk@kernel.org,
        linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
References: <20200513133845.244903-1-maco@android.com>
From:   Jens Axboe <axboe@kernel.dk>
Message-ID: <fe0b7bf9-07b1-9025-f9d6-7ace03c89a1f@kernel.dk>
Date:   Thu, 21 May 2020 08:21:01 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <20200513133845.244903-1-maco@android.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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