From: Ming Lei <ming.lei@redhat.com>
To: Keith Busch <kbusch@meta.com>
Cc: axboe@kernel.dk, asml.silence@gmail.com,
linux-block@vger.kernel.org, io-uring@vger.kernel.org,
linux-nvme@lists.infradead.org, csander@purestorage.com,
Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCHv8 1/6] io_uring/rw: move buffer_select outside generic prep
Date: Fri, 28 Feb 2025 16:10:54 +0800 [thread overview]
Message-ID: <Z8FvjnXq3RpX4eZ3@fedora> (raw)
In-Reply-To: <20250227223916.143006-2-kbusch@meta.com>
On Thu, Feb 27, 2025 at 02:39:11PM -0800, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
>
> Cleans up the generic rw prep to not require the do_import flag. Use a
> different prep function for callers that might need buffer select.
>
> Based-on-a-patch-by: Jens Axboe <axboe@kernel.dk>
> Signed-off-by: Keith Busch <kbusch@kernel.org>
> ---
Reviewed-by: Ming Lei <ming.lei@redhat.com>
thanks,
Ming
next prev parent reply other threads:[~2025-02-28 8:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 22:39 [PATCHv8 0/6] ublk zero copy support Keith Busch
2025-02-27 22:39 ` [PATCHv8 1/6] io_uring/rw: move buffer_select outside generic prep Keith Busch
2025-02-28 8:10 ` Ming Lei [this message]
2025-02-27 22:39 ` [PATCHv8 2/6] io_uring/rw: move fixed buffer import to issue path Keith Busch
2025-02-28 8:11 ` Ming Lei
2025-02-27 22:39 ` [PATCHv8 3/6] nvme: map uring_cmd data even if address is 0 Keith Busch
2025-02-27 22:39 ` [PATCHv8 4/6] io_uring: add support for kernel registered bvecs Keith Busch
2025-02-28 8:13 ` Ming Lei
2025-02-27 22:39 ` [PATCHv8 5/6] ublk: zc register/unregister bvec Keith Busch
2025-02-28 8:14 ` Ming Lei
2025-02-27 22:39 ` [PATCHv8 6/6] io_uring: cache nodes and mapped buffers Keith Busch
2025-02-27 23:50 ` Jens Axboe
2025-02-28 14:06 ` [PATCHv8 0/6] ublk zero copy support 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=Z8FvjnXq3RpX4eZ3@fedora \
--to=ming.lei@redhat.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=io-uring@vger.kernel.org \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.