From: Ming Lei <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Cc: Ming Lei <[email protected]>
Subject: [PATCH 0/2] liburing: test: replace ublk test with kernel selftests
Date: Wed, 19 Mar 2025 17:26:34 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Jens,
The 1st patch removes the liburing ublk test source, and the 2nd patch
adds the test back with the kernel ublk selftest source.
The original test case is covered, and io_uring kernel fixed buffer and
ublk zero copy is covered too.
Now the ublk source code is one generic ublk server implementation, and
test code is shell script, this way is flexible & easy to add new tests.
Thanks,
Ming
Ming Lei (2):
liburing: test: remove test/uring_cmd_ublk.c
liburing: test: replace ublk test with kernel selftests
.gitignore | 1 +
test/Makefile | 22 +-
test/runtests.sh | 8 +
test/ublk/file_backed.c | 217 ++++++
test/{uring_cmd_ublk.c => ublk/kublk.c} | 925 ++++++++++--------------
test/ublk/kublk.h | 336 +++++++++
test/ublk/null.c | 38 +
test/ublk/test_common.sh | 221 ++++++
test/ublk/test_stress_02.sh | 48 ++
9 files changed, 1286 insertions(+), 530 deletions(-)
create mode 100644 test/ublk/file_backed.c
rename test/{uring_cmd_ublk.c => ublk/kublk.c} (56%)
create mode 100644 test/ublk/kublk.h
create mode 100644 test/ublk/null.c
create mode 100755 test/ublk/test_common.sh
create mode 100755 test/ublk/test_stress_02.sh
--
2.47.0
next reply other threads:[~2025-03-19 9:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 9:26 Ming Lei [this message]
2025-03-19 9:26 ` [PATCH 1/2] liburing: test: remove test/uring_cmd_ublk.c Ming Lei
2025-03-19 9:26 ` [PATCH 2/2] liburing: test: replace ublk test with kernel selftests Ming Lei
2025-03-19 13:47 ` [PATCH 0/2] " Jens Axboe
2025-03-19 13:51 ` 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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