From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Daniel Wagner <dwagner@suse.de>
Cc: "hch@infradead.org" <hch@infradead.org>,
Stephen Zhang <starzhangzsd@gmail.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
Coly Li <colyli@fnnas.com>,
Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>
Subject: Re: [PATCH blktests v2 2/2] doc: document how to configure bcache tests
Date: Thu, 22 Jan 2026 08:08:36 +0000 [thread overview]
Message-ID: <aXHaP23d0ih-yLCH@shinmob> (raw)
In-Reply-To: <20260121-bcache-v2-2-b26af185e63a@suse.de>
On Jan 21, 2026 / 15:36, Daniel Wagner wrote:
> Add a bcache entry in running-tests which explains how to configure
> blktests for the bcache tests.
>
> Signed-off-by: Daniel Wagner <dwagner@suse.de>
> ---
> Documentation/running-tests.md | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/Documentation/running-tests.md b/Documentation/running-tests.md
> index f9da042bb3a0..c4abc6767cd0 100644
> --- a/Documentation/running-tests.md
> +++ b/Documentation/running-tests.md
> @@ -189,6 +189,22 @@ THROTL_BLKDEV_TYPES="sdebug" ./check throtl/
> THROTL_BLKDEV_TYPES="nullb sdebug" ./check throtl/
> ```
>
> +### bcache test configuration
> +
> +The bcache tests require multiple devices to run simultaneously. By default,
> +blktests executes each test case iteratively for every individual device listed
> +in TEST_DEVS. This standard behavior makes it impossible to pass a group of
> +devices into a single test via TEST_DEVS.
> +
> +To solve this, the TEST_CASE_DEV_ARRAY was introduced. This allows for custom
> +device configurations on a per-test basis. For bcache tests, a minimum of three
> +devices is required. Configuration Example
> +
> +Add the following to your configuration to define the devices used for all
> +bcache tests:
As you noted in the cover letter, TEST_CASE_DEV_ARRAY is already described in
running-tests.md. So I think this section can be some more concise. My quick
rewrite is as follows. If it makes sense for you, please consider to pick it up.
### Bcache test configuration
The bcache tests require multiple devices to run simultaneously. By default,
blktests run each test case for each device in TEST_DEVS. This behavior
prevents testing with multiple devices. The TEST_CASE_DEV_ARRAY resolves this by
enabling multiple device configurations per test. Bcache tests need at
least three devices, which can be specified in your configuration as follows:
> +
> +TEST_CASE_DEV_ARRAY[bcache/*]="/dev/nvme0n1 /dev/vdb /dev/vdc"
> +
> ### Normal user
>
> To run test cases which require normal user privilege, prepare a user and
>
> --
> 2.52.0
>
prev parent reply other threads:[~2026-01-22 8:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 14:36 [PATCH blktests v2 0/2] bcache: add bcache/001 Daniel Wagner
2026-01-21 14:36 ` [PATCH blktests v2 1/2] " Daniel Wagner
2026-01-21 16:08 ` Daniel Wagner
2026-01-22 8:05 ` Shinichiro Kawasaki
2026-01-22 10:28 ` Daniel Wagner
2026-01-21 14:36 ` [PATCH blktests v2 2/2] doc: document how to configure bcache tests Daniel Wagner
2026-01-22 8:08 ` Shinichiro Kawasaki [this message]
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=aXHaP23d0ih-yLCH@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=colyli@fnnas.com \
--cc=dwagner@suse.de \
--cc=hch@infradead.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=starzhangzsd@gmail.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