From: Uday Shankar <ushankar@purestorage.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
io-uring@vger.kernel.org, Pavel Begunkov <asml.silence@gmail.com>,
Caleb Sander Mateos <csander@purestorage.com>
Subject: Re: [PATCH 4/4] selftests: ublk: enable zero copy for stripe target
Date: Thu, 3 Apr 2025 16:42:40 -0600 [thread overview]
Message-ID: <Z+8O4Hro3QeNenjE@dev-ushankar.dev.purestorage.com> (raw)
In-Reply-To: <20250325135155.935398-5-ming.lei@redhat.com>
On Tue, Mar 25, 2025 at 09:51:53PM +0800, Ming Lei wrote:
> Use io_uring vectored fixed kernel buffer for handling stripe IO.
>
> Signed-off-by: Ming Lei <ming.lei@redhat.com>
> ---
> tools/testing/selftests/ublk/Makefile | 1 +
> tools/testing/selftests/ublk/stripe.c | 69 ++++++++++++++++++++-------
> 2 files changed, 53 insertions(+), 17 deletions(-)
>
> diff --git a/tools/testing/selftests/ublk/Makefile b/tools/testing/selftests/ublk/Makefile
> index d98680d64a2f..c7781efea0f3 100644
> --- a/tools/testing/selftests/ublk/Makefile
> +++ b/tools/testing/selftests/ublk/Makefile
> @@ -17,6 +17,7 @@ TEST_PROGS += test_loop_05.sh
> TEST_PROGS += test_stripe_01.sh
> TEST_PROGS += test_stripe_02.sh
> TEST_PROGS += test_stripe_03.sh
> +TEST_PROGS += test_stripe_04.sh
This patch is missing the new file test_stripe_04.sh, causing ublk
selftests to be broken on block/for-next. Can you fix?
next prev parent reply other threads:[~2025-04-03 22:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 13:51 [PATCH 0/4] io_uring: support vectored fixed kernel buffer Ming Lei
2025-03-25 13:51 ` [PATCH 1/4] io_uring: add validate_fixed_range() for validate fixed buffer Ming Lei
2025-03-25 16:00 ` Caleb Sander Mateos
2025-03-25 13:51 ` [PATCH 2/4] block: add for_each_mp_bvec() Ming Lei
2025-03-25 13:51 ` [PATCH 3/4] io_uring: support vectored kernel fixed buffer Ming Lei
2025-03-25 13:51 ` [PATCH 4/4] selftests: ublk: enable zero copy for stripe target Ming Lei
2025-04-03 22:42 ` Uday Shankar [this message]
2025-04-04 0:23 ` Ming Lei
2025-04-02 7:57 ` [PATCH 0/4] io_uring: support vectored fixed kernel buffer Ming Lei
2025-04-02 11:59 ` Jens Axboe
2025-04-02 12:13 ` Pavel Begunkov
2025-04-02 13:09 ` Jens Axboe
2025-04-02 13:12 ` 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=Z+8O4Hro3QeNenjE@dev-ushankar.dev.purestorage.com \
--to=ushankar@purestorage.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=io-uring@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