From: Caleb Sander Mateos <csander@purestorage.com>
To: Ming Lei <tom.leiming@gmail.com>, Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
Caleb Sander Mateos <csander@purestorage.com>
Subject: [PATCH 7.2 0/2] ublk: enable UBLK_F_SHMEM_ZC on zone appends
Date: Wed, 20 May 2026 14:36:52 -0600 [thread overview]
Message-ID: <20260520203654.1413640-1-csander@purestorage.com> (raw)
Commit 4d4a512a1f87 ("ublk: add PFN-based buffer matching in I/O path")
added support to ublk_setup_iod() for matching request buffers against
registered UBLK_F_SHMEM_ZC buffers, but missed adding it to
ublk_setup_iod_zoned() for zoned requests. ublk_setup_iod_zoned()
duplicates the code for initializing struct ublksrv_io_desc, making it
easy to forget to keep them in sync. Move the common code to a helper
function ublk_init_iod(). This allows zone appends to leverage the
shared memory zero copy optimization.
This series is based on "ublk: optimize ublk_rq_has_data()" [1]
[1]: https://lore.kernel.org/linux-block/20260513211846.1956810-1-csander@purestorage.com/
Caleb Sander Mateos (2):
ublk: move ublk_req_build_flags() earlier
ublk: factor out ublk_init_iod() helper
drivers/block/ublk_drv.c | 123 +++++++++++++++++++--------------------
1 file changed, 60 insertions(+), 63 deletions(-)
--
2.54.0
next reply other threads:[~2026-05-20 20:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 20:36 Caleb Sander Mateos [this message]
2026-05-20 20:36 ` [PATCH 7.2 1/2] ublk: move ublk_req_build_flags() earlier Caleb Sander Mateos
2026-05-20 20:36 ` [PATCH 7.2 2/2] ublk: factor out ublk_init_iod() helper Caleb Sander Mateos
2026-05-22 1:53 ` [PATCH 7.2 0/2] ublk: enable UBLK_F_SHMEM_ZC on zone appends Ming Lei
2026-05-22 14:06 ` 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=20260520203654.1413640-1-csander@purestorage.com \
--to=csander@purestorage.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.leiming@gmail.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