Re: [GIT PULL] Block changes for 6.18-rc1

[Jens Axboe <axboe@kernel.dk>]

On 9/29/25 7:50 PM, Caleb Sander Mateos wrote:
> On Mon, Sep 29, 2025 at 6:46?PM Jens Axboe <axboe@kernel.dk> wrote:
>>
>> Hi Linus,
>>
>> Here are the block changes scheduled for the 6.18 merge window. This
>> pull request contains:
>>
>> - NVMe pull request via Keith:
>>         - FC target fixes (Daniel)
>>         - Authentication fixes and updates (Martin, Chris)
>>         - Admin controller handling (Kamaljit)
>>         - Target lockdep assertions (Max)
>>         - Keep-alive updates for discovery (Alastair)
>>         - Suspend quirk (Georg)
>>
>> - MD pull request via Yu:
>>         - Add support for a lockless bitmap. Key features for the new
>>           bitmap are that the IO fastpath is lockless. If user issues
>>           lots of write IO to the same bitmap bit in a short time, only
>>           the first write has additional overhead to update bitmap bit,
>>           no additional overhead for the following writes. By supporting
>>           only resync or recover written data, means in the case
>>           creating new array or replacing with a new disk, there is no
>>           need to do a full disk resync/recovery.
>>
>> - Switch ->getgeo() and ->bios_param() to using struct gendisk rather
>>   than struct block_device.
>>
>> - Rust block changes via Andreas. This series adds configuration via
>>   configfs and remote completion to the rnull driver. The series also
>>   includes a set of changes to the rust block device driver API: a few
>>   cleanup patches, and a few features supporting the rnull changes.
>>
>>   The series removes the raw buffer formatting logic from
>>   `kernel::block` and improves the logic available in `kernel::string`
>>   to support the same use as the removed logic.
>>
>> - floppy arch cleanups
>>
>> - Add support for UBLK_F_BATCH_IO, improving the user <-> kernel
>>   communication
>>         - Per-queue vs Per-I/O: Commands operate on queues rather than
>>           individual I/Os
>>         - Batch processing: Multiple I/Os are handled in single
>>           operation
>>         - Multishot commands: Use io_uring multishot for reducing
>>           submission overhead
>>         - Flexible task assignment: Any task can handle any I/O
>>           (no per-I/O daemons)
>>         - Better load balancing: Tasks can adjust their workload
>>           dynamically
>>         - help for following future optimizations:
>>                 - blk-mq batch tags allocation/free,
>>                 - easier to support io-poll
>>                 - per-task batch for avoiding per-io lock
> 
> Perhaps I'm missing something, but I don't actually see the
> UBLK_F_BATCH_IO series in the list of commits. My understanding was
> that it's still in the process of being reviewed, I hadn't seen you
> apply it yet.

Yep you are totally right, that did not make it in. It was part of my
draft but never got it updated! Linus, please just edit this that part
out when pulling, thanks.

-- 
Jens Axboe