From: Daniel Wagner <dwagner@suse.de>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
Daniel Wagner <wagi@kernel.org>
Subject: [PATCH blktests 0/5] nvme: tests for isolated CPUs and fabrics queue mapping
Date: Wed, 14 Oct 2026 09:51:46 +0200 [thread overview]
Message-ID: <20261014-nvme-isolcpu-v1-0-2fd175a8ef00@kernel.org> (raw)
New tests for the bugs fixed by the kernel series "nvme-fabrics: fix
connects with isolated CPUs and queue mapping bugs":
https://lore.kernel.org/linux-nvme/20261014-nvme-fabrics-isolcpu-v1-0-355156be27b2@kernel.org/
nvme/070 connect with an isolated CPU (cpuset partition), verified
I/O from a housekeeping and from the isolated CPU, traced on
the queue of the isolated CPU
nvme/071 more write and poll queues than online CPUs
nvme/072 no queues left for polling
nvme/073 reconnect with fewer I/O queues
nvme/071-073 need write and poll queues and only run for tcp and rdma.
Without the kernel series all four fail and nvme/073 crashes the kernel,
with the series they pass. Tested with loop and tcp.
Patch 1 stops _nvme_disconnect_ctrl() and _nvme_disconnect_subsys() from
truncating $FULL, which dropped everything logged before the disconnect,
e.g. the fio command lines.
Signed-off-by: Daniel Wagner <wagi@kernel.org>
---
Daniel Wagner (5):
common/nvme: don't truncate the full log when disconnecting
nvme/070: test connect with an isolated CPU
nvme/071: test I/O queue limits per queue type
nvme/072: test poll support without poll queues
nvme/073: test reconnect with fewer I/O queues
common/nvme | 4 +-
tests/nvme/070 | 196 +++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/nvme/070.out | 2 +
tests/nvme/071 | 104 ++++++++++++++++++++++++++++
tests/nvme/071.out | 2 +
tests/nvme/072 | 85 +++++++++++++++++++++++
tests/nvme/072.out | 2 +
tests/nvme/073 | 117 ++++++++++++++++++++++++++++++++
tests/nvme/073.out | 2 +
9 files changed, 512 insertions(+), 2 deletions(-)
---
base-commit: 6f5a1dcb4551fe45c35e1fb1cdfa8343909f834a
change-id: 20261014-nvme-isolcpu-9f061e6a96ff
Best regards,
--
Daniel Wagner <wagi@kernel.org>
next reply other threads:[~2026-10-14 7:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 7:51 Daniel Wagner [this message]
2026-10-14 7:51 ` [PATCH blktests 1/5] common/nvme: don't truncate the full log when disconnecting Daniel Wagner
2026-10-14 7:51 ` [PATCH blktests 2/5] nvme/070: test connect with an isolated CPU Daniel Wagner
2026-10-14 7:51 ` [PATCH blktests 3/5] nvme/071: test I/O queue limits per queue type Daniel Wagner
2026-10-14 7:51 ` [PATCH blktests 4/5] nvme/072: test poll support without poll queues Daniel Wagner
2026-10-14 7:51 ` [PATCH blktests 5/5] nvme/073: test reconnect with fewer I/O queues Daniel Wagner
2026-10-20 6:40 ` [PATCH blktests 0/5] nvme: tests for isolated CPUs and fabrics queue mapping Shin'ichiro Kawasaki
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=20261014-nvme-isolcpu-v1-0-2fd175a8ef00@kernel.org \
--to=dwagner@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=shinichiro.kawasaki@wdc.com \
--cc=wagi@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 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.