From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Cc: Ming Lei <ming.lei@redhat.com>
Subject: [PATCH 0/8] selftests: ublk: cleanup & more tests
Date: Sat, 22 Mar 2025 17:32:08 +0800 [thread overview]
Message-ID: <20250322093218.431419-1-ming.lei@redhat.com> (raw)
Hi Jens,
The 1st patch adds generic_01.sh for checking if IO is dispatched in order.
The 2nd ~ 7th patches clean up and simplify target implementation, add zc
for for null, which is useful for evaluating/comparing perf.
The 8th patch adds ublk/stripe target and two tests, which will be useful
for verifying multiple IOs aiming at same fixed kernel buffer, also can
be used for verifying vectored fixed kernel buffer in future if this
feature can be supported.
Ming Lei (8):
selftests: ublk: add generic_01 for verifying sequential IO order
selftests: ublk: add single sqe allocator helper
selftests: ublk: increase max buffer size to 1MB
selftests: ublk: move common code into common.c
selftests: ublk: prepare for supporting stripe target
selftests: ublk: enable zero copy for null target
selftests: ublk: simplify loop io completion
selftests: ublk: add stripe target
tools/testing/selftests/ublk/Makefile | 9 +-
tools/testing/selftests/ublk/common.c | 55 +++
tools/testing/selftests/ublk/file_backed.c | 167 ++++-----
tools/testing/selftests/ublk/kublk.c | 33 +-
tools/testing/selftests/ublk/kublk.h | 85 +++--
tools/testing/selftests/ublk/null.c | 72 +++-
tools/testing/selftests/ublk/stripe.c | 318 ++++++++++++++++++
tools/testing/selftests/ublk/test_common.sh | 22 ++
.../testing/selftests/ublk/test_generic_01.sh | 44 +++
tools/testing/selftests/ublk/test_null_02.sh | 20 ++
.../testing/selftests/ublk/test_stripe_01.sh | 34 ++
.../testing/selftests/ublk/test_stripe_02.sh | 24 ++
tools/testing/selftests/ublk/trace/seq_io.bt | 25 ++
13 files changed, 759 insertions(+), 149 deletions(-)
create mode 100644 tools/testing/selftests/ublk/common.c
create mode 100644 tools/testing/selftests/ublk/stripe.c
create mode 100755 tools/testing/selftests/ublk/test_generic_01.sh
create mode 100755 tools/testing/selftests/ublk/test_null_02.sh
create mode 100755 tools/testing/selftests/ublk/test_stripe_01.sh
create mode 100755 tools/testing/selftests/ublk/test_stripe_02.sh
create mode 100644 tools/testing/selftests/ublk/trace/seq_io.bt
--
2.47.0
next reply other threads:[~2025-03-22 9:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 9:32 Ming Lei [this message]
2025-03-22 9:32 ` [PATCH 1/8] selftests: ublk: add generic_01 for verifying sequential IO order Ming Lei
2025-03-22 9:32 ` [PATCH 2/8] selftests: ublk: add single sqe allocator helper Ming Lei
2025-03-22 9:32 ` [PATCH 3/8] selftests: ublk: increase max buffer size to 1MB Ming Lei
2025-03-22 9:32 ` [PATCH 4/8] selftests: ublk: move common code into common.c Ming Lei
2025-03-22 9:32 ` [PATCH 5/8] selftests: ublk: prepare for supporting stripe target Ming Lei
2025-03-22 9:32 ` [PATCH 6/8] selftests: ublk: enable zero copy for null target Ming Lei
2025-03-22 9:32 ` [PATCH 7/8] selftests: ublk: simplify loop io completion Ming Lei
2025-03-22 9:32 ` [PATCH 8/8] selftests: ublk: add stripe target Ming Lei
2025-03-22 14:35 ` [PATCH 0/8] selftests: ublk: cleanup & more tests 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=20250322093218.431419-1-ming.lei@redhat.com \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox