From: John Garry <john.g.garry@oracle.com>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH blktests 0/7] Further stacked device atomic writes testing
Date: Thu, 18 Sep 2025 08:48:20 +0100 [thread overview]
Message-ID: <c21f0ffa-5027-4bfe-a6f0-6744d9fbed33@oracle.com> (raw)
In-Reply-To: <zk2a2pficfjptjkjsx2wd6kxh5padaop7ge7n2georpofke4fr@lzdzzdmef7qu>
On 18/09/2025 05:36, Shinichiro Kawasaki wrote:
> On Sep 17, 2025 / 17:22, John Garry wrote:
>> On 17/09/2025 14:12, John Garry wrote:
>>>> It also has slightly different variables for use in the
>>>> test_device_array()
>>>> function: TEST_DEV_ARRAY and TEST_DEV_ARRAY_SYSFS_DIRS. As an
>>>> example, I made a
>>>> quick commit on top of your patches [4].
>>>>
>>>> [4]https://urldefense.com/v3/__https://github.com/kawasaki/blktests/
>>>> commit/
>>>> fae0b3b617a19dab60610f50361bb0da6e0543ea__;!!ACWV5N9M2RV99hQ!
>>>> NNGuj9SVoLIwKksQudWC5ktgS6vIXTX1dGSmibli2-httSpUBfSHAIL1i2z-
>>>> aCmYSXUZxmwGZswO2KJ6Ei8gwmoYAPTl$
>>>> I will review details of your patches tomorrow.
>>>
>>> great, thanks.
>>>
>>> I'll test md/002 and md/003 today with all these changes.
>>
>> I gave it a quick spin and it looks to work ok.
>
> Good to hear, thanks.
>
>>
>> About TEST_CASE_DEV_ARRAY, is it scalable to index this per test case?
>
> I'm not exactly sure what you mean with the word "scalable", but I guess
> you worry about many config lines of TEST_CASE_DEV_ARRAY[X]=Y for many test
> cases with test_device_array().
Yes
> The series allows the keys X of
> TEST_CASE_DEV_ARRAY can be regular expressions, I think many of the config
> lines can be combined into single line when they use the same devices Y.
How would that look then in the config file? More examples could help me
see your idea.
>
> BTW, I made the detailed comments on your patches. Other than the comments
> and the adaptations to the test_device_array(), the series looks good to me.
> Thanks!
thanks for the help
How to co-ordinate posting and merging of these series?
Shall I repost mine based on yours?
Thanks,
John
next prev parent reply other threads:[~2025-09-18 7:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 9:57 [PATCH blktests 0/7] Further stacked device atomic writes testing John Garry
2025-09-12 9:57 ` [PATCH blktests 1/7] common/rc: add _min() John Garry
2025-09-18 4:08 ` Shinichiro Kawasaki
2025-09-18 7:33 ` John Garry
2025-09-12 9:57 ` [PATCH blktests 2/7] md/rc: add _md_atomics_test John Garry
2025-09-18 4:17 ` Shinichiro Kawasaki
2025-09-18 7:36 ` John Garry
2025-09-12 9:57 ` [PATCH blktests 3/7] md/002: convert to use _md_atomics_test John Garry
2025-09-12 9:57 ` [PATCH blktests 4/7] md/003: add NVMe atomic write tests for stacked devices John Garry
2025-09-18 4:27 ` Shinichiro Kawasaki
2025-09-18 7:44 ` John Garry
2025-09-12 9:57 ` [PATCH blktests 5/7] md/rc: test atomic writes for dm-linear John Garry
2025-09-12 9:57 ` [PATCH blktests 6/7] md/rc: test atomic writes for dm-stripe John Garry
2025-09-12 9:57 ` [PATCH blktests 7/7] md/rc: test atomic writes for dm-mirror John Garry
2025-09-16 8:55 ` [PATCH blktests 0/7] Further stacked device atomic writes testing Shinichiro Kawasaki
2025-09-16 10:20 ` John Garry
2025-09-16 11:55 ` John Garry
2025-09-16 12:23 ` Shinichiro Kawasaki
2025-09-16 12:27 ` John Garry
2025-09-17 12:02 ` Shinichiro Kawasaki
2025-09-17 13:12 ` John Garry
2025-09-17 16:22 ` John Garry
2025-09-18 4:36 ` Shinichiro Kawasaki
2025-09-18 7:48 ` John Garry [this message]
2025-09-18 10:37 ` Shinichiro 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=c21f0ffa-5027-4bfe-a6f0-6744d9fbed33@oracle.com \
--to=john.g.garry@oracle.com \
--cc=linux-block@vger.kernel.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