public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Caleb Sander Mateos <csander@purestorage.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org,
	Uday Shankar <ushankar@purestorage.com>,
	Stefani Seibold <stefani@seibold.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4 16/27] ublk: add new feature UBLK_F_BATCH_IO
Date: Wed, 3 Dec 2025 10:21:39 +0800	[thread overview]
Message-ID: <aS-es2I_f6d_H_C9@fedora> (raw)
In-Reply-To: <CADUfDZqRQ3WmwswwfQf_vhP84OVmwU3LGMF8Rb8mShQSjnZAJQ@mail.gmail.com>

On Tue, Dec 02, 2025 at 08:05:17AM -0800, Caleb Sander Mateos wrote:
> On Mon, Dec 1, 2025 at 5:44 PM Ming Lei <ming.lei@redhat.com> wrote:
> >
> > On Mon, Dec 01, 2025 at 01:16:04PM -0800, Caleb Sander Mateos wrote:
> > > On Thu, Nov 20, 2025 at 6:00 PM Ming Lei <ming.lei@redhat.com> wrote:
> > > >
> > > > Add new feature UBLK_F_BATCH_IO which replaces the following two
> > > > per-io commands:
> > > >
> > > >         - UBLK_U_IO_FETCH_REQ
> > > >
> > > >         - UBLK_U_IO_COMMIT_AND_FETCH_REQ
> > > >
> > > > with three per-queue batch io uring_cmd:
> > > >
> > > >         - UBLK_U_IO_PREP_IO_CMDS
> > > >
> > > >         - UBLK_U_IO_COMMIT_IO_CMDS
> > > >
> > > >         - UBLK_U_IO_FETCH_IO_CMDS
> > > >
> > > > Then ublk can deliver batch io commands to ublk server in single
> > > > multishort uring_cmd, also allows to prepare & commit multiple
> > > > commands in batch style via single uring_cmd, communication cost is
> > > > reduced a lot.
> > > >
> > > > This feature also doesn't limit task context any more for all supported
> > > > commands, so any allowed uring_cmd can be issued in any task context.
> > > > ublk server implementation becomes much easier.
> > > >
> > > > Meantime load balance becomes much easier to support with this feature.
> > > > The command `UBLK_U_IO_FETCH_IO_CMDS` can be issued from multiple task
> > > > contexts, so each task can adjust this command's buffer length or number
> > > > of inflight commands for controlling how much load is handled by current
> > > > task.
> > > >
> > > > Later, priority parameter will be added to command `UBLK_U_IO_FETCH_IO_CMDS`
> > > > for improving load balance support.
> > > >
> > > > UBLK_U_IO_GET_DATA isn't supported in batch io yet, but it may be
> > >
> > > UBLK_U_IO_NEED_GET_DATA?
> >
> > Yeah.
> >
> > >
> > > > enabled in future via its batch pair.
> > > >
> > > > Signed-off-by: Ming Lei <ming.lei@redhat.com>
> > > > ---
> > > >  drivers/block/ublk_drv.c      | 58 ++++++++++++++++++++++++++++++++---
> > > >  include/uapi/linux/ublk_cmd.h | 16 ++++++++++
> > > >  2 files changed, 69 insertions(+), 5 deletions(-)
> > > >
> > > > diff --git a/drivers/block/ublk_drv.c b/drivers/block/ublk_drv.c
> > > > index 849199771f86..90cd1863bc83 100644
> > > > --- a/drivers/block/ublk_drv.c
> > > > +++ b/drivers/block/ublk_drv.c
> > > > @@ -74,7 +74,8 @@
> > > >                 | UBLK_F_AUTO_BUF_REG \
> > > >                 | UBLK_F_QUIESCE \
> > > >                 | UBLK_F_PER_IO_DAEMON \
> > > > -               | UBLK_F_BUF_REG_OFF_DAEMON)
> > > > +               | UBLK_F_BUF_REG_OFF_DAEMON \
> > > > +               | UBLK_F_BATCH_IO)
> > > >
> > > >  #define UBLK_F_ALL_RECOVERY_FLAGS (UBLK_F_USER_RECOVERY \
> > > >                 | UBLK_F_USER_RECOVERY_REISSUE \
> > > > @@ -320,12 +321,12 @@ static void ublk_batch_dispatch(struct ublk_queue *ubq,
> > > >
> > > >  static inline bool ublk_dev_support_batch_io(const struct ublk_device *ub)
> > > >  {
> > > > -       return false;
> > > > +       return ub->dev_info.flags & UBLK_F_BATCH_IO;
> > > >  }
> > > >
> > > >  static inline bool ublk_support_batch_io(const struct ublk_queue *ubq)
> > > >  {
> > > > -       return false;
> > > > +       return ubq->flags & UBLK_F_BATCH_IO;
> > > >  }
> > > >
> > > >  static inline void ublk_io_lock(struct ublk_io *io)
> > > > @@ -3450,6 +3451,41 @@ static int ublk_validate_batch_fetch_cmd(struct ublk_batch_io_data *data,
> > > >         return 0;
> > > >  }
> > > >
> > > > +static int ublk_handle_non_batch_cmd(struct io_uring_cmd *cmd,
> > > > +                                    unsigned int issue_flags)
> > > > +{
> > > > +       const struct ublksrv_io_cmd *ub_cmd = io_uring_sqe_cmd(cmd->sqe);
> > > > +       struct ublk_device *ub = cmd->file->private_data;
> > > > +       unsigned tag = READ_ONCE(ub_cmd->tag);
> > > > +       unsigned q_id = READ_ONCE(ub_cmd->q_id);
> > > > +       unsigned index = READ_ONCE(ub_cmd->addr);
> > > > +       struct ublk_queue *ubq;
> > > > +       struct ublk_io *io;
> > > > +       int ret = -EINVAL;
> > >
> > > I think it would be clearer to just return -EINVAL instead of adding
> > > this variable, but up to you
> > >
> > > > +
> > > > +       if (!ub)
> > > > +               return ret;
> > >
> > > How is this case possible?
> >
> > Will remove the check.
> >
> > >
> > > > +
> > > > +       if (q_id >= ub->dev_info.nr_hw_queues)
> > > > +               return ret;
> > > > +
> > > > +       ubq = ublk_get_queue(ub, q_id);
> > > > +       if (tag >= ubq->q_depth)
> > >
> > > Can avoid the likely cache miss here by using ub->dev_info.queue_depth
> > > instead, analogous to ublk_ch_uring_cmd_local()
> >
> > OK.
> >
> > >
> > > > +               return ret;
> > > > +
> > > > +       io = &ubq->ios[tag];
> > > > +
> > > > +       switch (cmd->cmd_op) {
> > > > +       case UBLK_U_IO_REGISTER_IO_BUF:
> > > > +               return ublk_register_io_buf(cmd, ub, q_id, tag, io, index,
> > > > +                               issue_flags);
> > > > +       case UBLK_U_IO_UNREGISTER_IO_BUF:
> > > > +               return ublk_unregister_io_buf(cmd, ub, index, issue_flags);
> > > > +       default:
> > > > +               return -EOPNOTSUPP;
> > > > +       }
> > > > +}
> > > > +
> > > >  static int ublk_ch_batch_io_uring_cmd(struct io_uring_cmd *cmd,
> > > >                                        unsigned int issue_flags)
> > > >  {
> > > > @@ -3497,7 +3533,8 @@ static int ublk_ch_batch_io_uring_cmd(struct io_uring_cmd *cmd,
> > > >                 ret = ublk_handle_batch_fetch_cmd(&data);
> > > >                 break;
> > > >         default:
> > > > -               ret = -EOPNOTSUPP;
> > > > +               ret = ublk_handle_non_batch_cmd(cmd, issue_flags);
> > >
> > > We should probably skip the if (data.header.q_id >=
> > > ub->dev_info.nr_hw_queues) check for a non-batch command?
> >
> > It is true only for UBLK_IO_UNREGISTER_IO_BUF.
> 
> My point was that this relies on the q_id field being located at the
> same offset in struct ublksrv_io_cmd and struct ublk_batch_io, which
> seems quite subtle. I think it would make more sense not to read the
> SQE as a struct ublk_batch_io for the non-batch commands.

OK, got it, then the check can be moved to ublk_check_batch_cmd() and
ublk_validate_batch_fetch_cmd(). It can be one delta fix for V5.


Thanks,
Ming


  reply	other threads:[~2025-12-03  2:21 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21  1:58 [PATCH V4 00/27] ublk: add UBLK_F_BATCH_IO Ming Lei
2025-11-21  1:58 ` [PATCH V4 01/27] kfifo: add kfifo_alloc_node() helper for NUMA awareness Ming Lei
2025-11-29 19:12   ` Caleb Sander Mateos
2025-12-01  1:46     ` Ming Lei
2025-12-01  5:58       ` Caleb Sander Mateos
2025-11-21  1:58 ` [PATCH V4 02/27] ublk: add parameter `struct io_uring_cmd *` to ublk_prep_auto_buf_reg() Ming Lei
2025-11-21  1:58 ` [PATCH V4 03/27] ublk: add `union ublk_io_buf` with improved naming Ming Lei
2025-11-21  1:58 ` [PATCH V4 04/27] ublk: refactor auto buffer register in ublk_dispatch_req() Ming Lei
2025-11-21  1:58 ` [PATCH V4 05/27] ublk: pass const pointer to ublk_queue_is_zoned() Ming Lei
2025-11-21  1:58 ` [PATCH V4 06/27] ublk: add helper of __ublk_fetch() Ming Lei
2025-11-21  1:58 ` [PATCH V4 07/27] ublk: define ublk_ch_batch_io_fops for the coming feature F_BATCH_IO Ming Lei
2025-11-21  1:58 ` [PATCH V4 08/27] ublk: prepare for not tracking task context for command batch Ming Lei
2025-11-21  1:58 ` [PATCH V4 09/27] ublk: add new batch command UBLK_U_IO_PREP_IO_CMDS & UBLK_U_IO_COMMIT_IO_CMDS Ming Lei
2025-11-29 19:19   ` Caleb Sander Mateos
2025-11-21  1:58 ` [PATCH V4 10/27] ublk: handle UBLK_U_IO_PREP_IO_CMDS Ming Lei
2025-11-29 19:47   ` Caleb Sander Mateos
2025-11-30 19:25   ` Caleb Sander Mateos
2025-11-21  1:58 ` [PATCH V4 11/27] ublk: handle UBLK_U_IO_COMMIT_IO_CMDS Ming Lei
2025-11-30 16:39   ` Caleb Sander Mateos
2025-12-01 10:25     ` Ming Lei
2025-12-01 16:43       ` Caleb Sander Mateos
2025-11-21  1:58 ` [PATCH V4 12/27] ublk: add io events fifo structure Ming Lei
2025-11-30 16:53   ` Caleb Sander Mateos
2025-12-01  3:04     ` Ming Lei
2025-11-21  1:58 ` [PATCH V4 13/27] ublk: add batch I/O dispatch infrastructure Ming Lei
2025-11-30 19:24   ` Caleb Sander Mateos
2025-11-30 21:37     ` Caleb Sander Mateos
2025-12-01  2:32     ` Ming Lei
2025-12-01 17:37       ` Caleb Sander Mateos
2025-11-21  1:58 ` [PATCH V4 14/27] ublk: add UBLK_U_IO_FETCH_IO_CMDS for batch I/O processing Ming Lei
2025-12-01  5:55   ` Caleb Sander Mateos
2025-12-01  9:41     ` Ming Lei
2025-12-01 17:51       ` Caleb Sander Mateos
2025-12-02  1:27         ` Ming Lei
2025-12-02  1:39           ` Caleb Sander Mateos
2025-12-02  8:14             ` Ming Lei
2025-12-02 15:20               ` Caleb Sander Mateos
2025-11-21  1:58 ` [PATCH V4 15/27] ublk: abort requests filled in event kfifo Ming Lei
2025-12-01 18:52   ` Caleb Sander Mateos
2025-12-02  1:29     ` Ming Lei
2025-12-01 19:00   ` Caleb Sander Mateos
2025-11-21  1:58 ` [PATCH V4 16/27] ublk: add new feature UBLK_F_BATCH_IO Ming Lei
2025-12-01 21:16   ` Caleb Sander Mateos
2025-12-02  1:44     ` Ming Lei
2025-12-02 16:05       ` Caleb Sander Mateos
2025-12-03  2:21         ` Ming Lei [this message]
2025-11-21  1:58 ` [PATCH V4 17/27] ublk: document " Ming Lei
2025-12-01 21:46   ` Caleb Sander Mateos
2025-12-02  1:55     ` Ming Lei
2025-12-02  2:03     ` Ming Lei
2025-11-21  1:58 ` [PATCH V4 18/27] ublk: implement batch request completion via blk_mq_end_request_batch() Ming Lei
2025-12-01 21:55   ` Caleb Sander Mateos
2025-11-21  1:58 ` [PATCH V4 19/27] selftests: ublk: fix user_data truncation for tgt_data >= 256 Ming Lei
2025-11-21  1:58 ` [PATCH V4 20/27] selftests: ublk: replace assert() with ublk_assert() Ming Lei
2025-11-21  1:58 ` [PATCH V4 21/27] selftests: ublk: add ublk_io_buf_idx() for returning io buffer index Ming Lei
2025-11-21  1:58 ` [PATCH V4 22/27] selftests: ublk: add batch buffer management infrastructure Ming Lei
2025-11-21  1:58 ` [PATCH V4 23/27] selftests: ublk: handle UBLK_U_IO_PREP_IO_CMDS Ming Lei
2025-11-21  1:58 ` [PATCH V4 24/27] selftests: ublk: handle UBLK_U_IO_COMMIT_IO_CMDS Ming Lei
2025-11-21  1:58 ` [PATCH V4 25/27] selftests: ublk: handle UBLK_U_IO_FETCH_IO_CMDS Ming Lei
2025-11-21  1:58 ` [PATCH V4 26/27] selftests: ublk: add --batch/-b for enabling F_BATCH_IO Ming Lei
2025-11-21  1:58 ` [PATCH V4 27/27] selftests: ublk: support arbitrary threads/queues combination Ming Lei
2025-11-28 11:59 ` [PATCH V4 00/27] ublk: add UBLK_F_BATCH_IO Ming Lei
2025-11-28 16:19   ` Jens Axboe
2025-11-28 19:07     ` Caleb Sander Mateos
2025-11-29  1:24       ` Ming Lei
2025-11-28 16:22 ` (subset) " Jens Axboe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aS-es2I_f6d_H_C9@fedora \
    --to=ming.lei@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=csander@purestorage.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefani@seibold.net \
    --cc=ushankar@purestorage.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox