From: Jens Axboe <axboe@kernel.dk>
To: Caleb Sander Mateos <csander@purestorage.com>,
Ming Lei <ming.lei@redhat.com>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] Minor ublk optimizations
Date: Fri, 28 Mar 2025 13:20:59 -0600 [thread overview]
Message-ID: <31fe911c-7340-4687-a384-c67cfc4b6380@kernel.dk> (raw)
In-Reply-To: <20250328180411.2696494-1-csander@purestorage.com>
On 3/28/25 12:04 PM, Caleb Sander Mateos wrote:
> A few cleanups on top of Ming's recent patch set that implemented
> ->queue_rqs() for ublk:
> https://lore.kernel.org/linux-block/20250327095123.179113-1-ming.lei@redhat.com/T/#u
>
> Caleb Sander Mateos (5):
> ublk: remove unused cmd argument to ublk_dispatch_req()
> ublk: skip 1 NULL check in ublk_cmd_list_tw_cb() loop
> ublk: get ubq from pdu in ublk_cmd_list_tw_cb()
> ublk: avoid redundant io->cmd in ublk_queue_cmd_list()
> ublk: store req in ublk_uring_cmd_pdu for ublk_cmd_tw_cb()
All look like reasonable cleanups to me.
--
Jens Axboe
next prev parent reply other threads:[~2025-03-28 19:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 18:04 [PATCH 0/5] Minor ublk optimizations Caleb Sander Mateos
2025-03-28 18:04 ` [PATCH 1/5] ublk: remove unused cmd argument to ublk_dispatch_req() Caleb Sander Mateos
2025-03-28 18:04 ` [PATCH 2/5] ublk: skip 1 NULL check in ublk_cmd_list_tw_cb() loop Caleb Sander Mateos
2025-03-28 18:04 ` [PATCH 3/5] ublk: get ubq from pdu in ublk_cmd_list_tw_cb() Caleb Sander Mateos
2025-03-28 18:04 ` [PATCH 4/5] ublk: avoid redundant io->cmd in ublk_queue_cmd_list() Caleb Sander Mateos
2025-03-28 18:04 ` [PATCH 5/5] ublk: store req in ublk_uring_cmd_pdu for ublk_cmd_tw_cb() Caleb Sander Mateos
2025-03-28 19:20 ` Jens Axboe [this message]
2025-03-29 0:23 ` [PATCH 0/5] Minor ublk optimizations Ming Lei
2025-03-29 11:57 ` 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=31fe911c-7340-4687-a384-c67cfc4b6380@kernel.dk \
--to=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.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