From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Daniel Wagner <dwagner@suse.de>
Cc: "kanie@linux.alibaba.com" <kanie@linux.alibaba.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"shinichiro.kawasaki@wdc.com" <shinichiro.kawasaki@wdc.com>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>
Subject: Re: [PATCH] nvme: test nvmet-wq sysfs interface
Date: Wed, 6 Nov 2024 03:46:26 +0000 [thread overview]
Message-ID: <bd5ea038-42ab-433a-943f-d385ccd96770@nvidia.com> (raw)
In-Reply-To: <5d603860-33be-42a2-86c9-a10c224c813d@flourine.local>
On 11/4/24 23:02, Daniel Wagner wrote:
> On Mon, Nov 04, 2024 at 11:29:07AM GMT, Chaitanya Kulkarni wrote:
>> +# Test nvmet-wq cpumask sysfs attribute with NVMe-oF and fio workload
> What do you want to test here? What's the objective? I don't see any
> block layer related parts or do I miss something?
For NVMeOF target we have exported nvmet-wq to userspace with
recent patch. This behavior is new and I don't think there is any test
exists that runs the fio workload while changing the CPUMASK randomly
to ensure the stability for nvmet-wq when application is using the block
layer. Hence we need the test for latest patch we have added to the 6.13.
-ck
next prev parent reply other threads:[~2024-11-06 3:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 19:29 [PATCH] nvme: test nvmet-wq sysfs interface Chaitanya Kulkarni
2024-11-05 7:02 ` Daniel Wagner
2024-11-06 3:46 ` Chaitanya Kulkarni [this message]
2024-11-06 12:13 ` Daniel Wagner
2024-11-08 5:00 ` Shinichiro Kawasaki
2024-11-08 5:21 ` Shinichiro Kawasaki
2024-11-12 0:58 ` 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=bd5ea038-42ab-433a-943f-d385ccd96770@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=dwagner@suse.de \
--cc=kanie@linux.alibaba.com \
--cc=linux-block@vger.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