From: Daniel Wagner <dwagner@suse.de>
To: Keith Busch <kbusch@kernel.org>
Cc: linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>,
Martin Belanger <Martin.Belanger@dell.com>,
Daniel Wagner <dwagner@suse.de>
Subject: [PATCH v1 0/2] Test different queue counts
Date: Mon, 20 Mar 2023 18:38:04 +0100 [thread overview]
Message-ID: <20230320173806.12784-1-dwagner@suse.de> (raw)
In-Reply-To: <20230320152204.g27a6jqbb65xmb6r@carbon.lan>
Here is a rough version which tests the different types.
There are a couple problems with this version:
- works only for fabrics transports and not loop. I haven't figured out how
to express this in the requires()
- let's the kernel crash in various ways
Daniel Wagner (2):
nvme/rc: Parse optional arguments in _nvme_connect_subsys()
nvme/047: Test different queue counts
tests/nvme/047 | 65 ++++++++++++++++++++++++++++++++++++++++++++++
tests/nvme/047.out | 2 ++
tests/nvme/rc | 46 ++++++++++++++++++++++++++++++++
3 files changed, 113 insertions(+)
create mode 100755 tests/nvme/047
create mode 100644 tests/nvme/047.out
--
2.40.0
next prev parent reply other threads:[~2023-03-20 17:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 14:19 nvme-tcp poll queue crash Daniel Wagner
2023-03-20 14:36 ` Sagi Grimberg
2023-03-20 14:51 ` Daniel Wagner
2023-03-20 15:06 ` Keith Busch
2023-03-20 15:22 ` Daniel Wagner
2023-03-20 17:38 ` Daniel Wagner [this message]
2023-03-20 17:38 ` [PATCH v1 1/2] nvme/rc: Parse optional arguments in _nvme_connect_subsys() Daniel Wagner
2023-03-21 5:16 ` Chaitanya Kulkarni
2023-03-21 7:20 ` Daniel Wagner
2023-03-22 5:17 ` Chaitanya Kulkarni
2023-03-20 17:38 ` [PATCH v1 2/2] nvme/047: Test different queue counts Daniel Wagner
2023-03-20 20:00 ` nvme-tcp poll queue crash Sagi Grimberg
2023-03-20 20:01 ` Sagi Grimberg
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=20230320173806.12784-1-dwagner@suse.de \
--to=dwagner@suse.de \
--cc=Martin.Belanger@dell.com \
--cc=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=shinichiro.kawasaki@wdc.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