From: Martin Wilck <mwilck@suse.com>
To: Daniel Wagner <dwagner@suse.de>
Cc: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
Hannes Reinecke <hare@suse.de>,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [PATCH 3/3] nvme: add test for controller rescan under I/O load
Date: Fri, 23 Aug 2024 08:50:04 +0200 [thread overview]
Message-ID: <746c53383557efde6bfa09e2bd848b553f88ff3a.camel@suse.com> (raw)
In-Reply-To: <9e199fd0-5767-4a63-930a-b08e89e4e354@flourine.local>
On Fri, 2024-08-23 at 08:45 +0200, Daniel Wagner wrote:
> On Thu, Aug 22, 2024 at 09:38:14PM GMT, Martin Wilck wrote:
> > Add a test that repeatedly rescans nvme controllers while doing IO
> > on an nvme namespace connected to these controllers. The purpose
> > of the test is to make sure that no I/O errors or data corruption
> > occurs because of the rescan operations.
>
> Could you elaborate why this tests is added? Does it test for a
> regression, are there any patches for this? Or is it more let's
> ensure
> this actually works?
The rationale was to test the kernel patch that I submitted yesterday:
https://lore.kernel.org/linux-nvme/9de89e5a-04fc-4684-8514-b86884643a5d@suse.de/T/#t
Thanks,
Martin
next prev parent reply other threads:[~2024-08-23 6:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 19:38 [PATCH 1/3] blktests: nvme: skip passthru tests on multipath devices Martin Wilck
2024-08-22 19:38 ` [PATCH 2/3] blktests: nvme/032: skip on non-PCI devices Martin Wilck
2024-08-23 6:46 ` Daniel Wagner
2024-08-22 19:38 ` [PATCH 3/3] nvme: add test for controller rescan under I/O load Martin Wilck
2024-08-23 6:45 ` Daniel Wagner
2024-08-23 6:50 ` Martin Wilck [this message]
2024-08-23 7:03 ` Daniel Wagner
2024-08-23 10:18 ` Nilay Shroff
2024-08-23 13:39 ` Nilay Shroff
2024-08-23 14:49 ` Martin Wilck
2024-08-23 6:35 ` [PATCH 1/3] blktests: nvme: skip passthru tests on multipath devices Daniel Wagner
2024-08-23 6:41 ` Martin Wilck
2024-08-23 7:07 ` Daniel Wagner
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=746c53383557efde6bfa09e2bd848b553f88ff3a.camel@suse.com \
--to=mwilck@suse.com \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--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