From: Daniel Wagner <dwagner@suse.de>
To: linux-nvme@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Chaitanya Kulkarni <kch@nvidia.com>,
Shin'ichiro Kawasaki <shinichiro@fastmail.com>,
Hannes Reinecke <hare@suse.de>, Daniel Wagner <dwagner@suse.de>
Subject: [PATCH blktests v3 06/12] Documentation: Add info on nvme_tr_type
Date: Wed, 3 May 2023 10:02:52 +0200 [thread overview]
Message-ID: <20230503080258.14525-7-dwagner@suse.de> (raw)
In-Reply-To: <20230503080258.14525-1-dwagner@suse.de>
Mention that the nvme tests can be parametrized.
Signed-off-by: Daniel Wagner <dwagner@suse.de>
---
Documentation/running-tests.md | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/running-tests.md b/Documentation/running-tests.md
index 3550f377f487..7e827fba7ac0 100644
--- a/Documentation/running-tests.md
+++ b/Documentation/running-tests.md
@@ -98,6 +98,13 @@ requires that the kernel be compiled with `CONFIG_BLK_DEV_ZONED` enabled.
RUN_ZONED_TESTS=1
```
+### NVMe test parameterizing
+
+The NVMe tests can be additionally parameterized via environment variables.
+
+- nvme_tr_type: 'loop' (default), 'tcp', 'rdma' and 'fc'
+ Run the tests with the given transport.
+
### Running nvme-rdma nvmeof-mp srp tests
Most of these tests will use the rdma_rxe (soft-RoCE) driver by default. The siw (soft-iWARP) driver is also supported.
--
2.40.0
next prev parent reply other threads:[~2023-05-03 8:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 8:02 [PATCH blktests v3 00/12] nvme testsuite runtime optimization Daniel Wagner
2023-05-03 8:02 ` [PATCH blktests v3 01/12] nvme/rc: Auto convert test device size info Daniel Wagner
2023-05-03 9:22 ` Chaitanya Kulkarni
2023-05-03 9:26 ` Daniel Wagner
2023-05-07 22:49 ` Shinichiro Kawasaki
2023-05-03 8:02 ` [PATCH blktests v3 02/12] nvme: Do not hard code device size for dd test Daniel Wagner
2023-05-03 9:23 ` Chaitanya Kulkarni
2023-05-07 22:51 ` Shinichiro Kawasaki
2023-05-03 8:02 ` [PATCH blktests v3 03/12] common/xfs: Make size argument optional for _xfs_run_fio_verify_io Daniel Wagner
2023-05-03 9:25 ` Chaitanya Kulkarni
2023-05-03 8:02 ` [PATCH blktests v3 04/12] common/xfs: Limit fio size job to fit into xfs fs Daniel Wagner
2023-05-03 9:29 ` Chaitanya Kulkarni
2023-05-03 9:42 ` Daniel Wagner
2023-05-03 8:02 ` [PATCH blktests v3 05/12] nvme: Use runtime fio background jobs Daniel Wagner
2023-05-07 22:56 ` Shinichiro Kawasaki
2023-05-03 8:02 ` Daniel Wagner [this message]
2023-05-03 9:32 ` [PATCH blktests v3 06/12] Documentation: Add info on nvme_tr_type Chaitanya Kulkarni
2023-05-07 23:21 ` Shinichiro Kawasaki
2023-05-03 8:02 ` [PATCH blktests v3 07/12] nvme: Make test image size configurable Daniel Wagner
2023-05-03 9:32 ` Chaitanya Kulkarni
2023-05-07 23:09 ` Shinichiro Kawasaki
2023-05-03 8:02 ` [PATCH blktests v3 08/12] nvme/rc: Add minimal test image size requirement Daniel Wagner
2023-05-03 9:35 ` Chaitanya Kulkarni
2023-05-07 23:19 ` Shinichiro Kawasaki
2023-05-03 8:02 ` [PATCH blktests v3 09/12] common/fio: Limit number of random jobs Daniel Wagner
2023-05-03 9:41 ` Chaitanya Kulkarni
2023-05-03 11:01 ` Daniel Wagner
2023-05-04 5:16 ` Chaitanya Kulkarni
2023-05-04 6:07 ` Daniel Wagner
2023-05-03 8:02 ` [PATCH blktests v3 10/12] nvme/rc: Calculate IO size for random fio jobs Daniel Wagner
2023-05-07 23:31 ` Shinichiro Kawasaki
2023-05-10 17:14 ` Daniel Wagner
2023-05-03 8:02 ` [PATCH blktests v3 11/12] nvme/rc: Move discovery generation counter code to rc Daniel Wagner
2023-05-07 23:34 ` Shinichiro Kawasaki
2023-05-10 17:24 ` Daniel Wagner
2023-05-11 16:44 ` Shinichiro Kawasaki
2023-05-03 8:02 ` [PATCH blktests v3 12/12] nvme: Make the number iterations configurable Daniel Wagner
2023-05-03 9:45 ` Chaitanya Kulkarni
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=20230503080258.14525-7-dwagner@suse.de \
--to=dwagner@suse.de \
--cc=hare@suse.de \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=shinichiro@fastmail.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