From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Daniel Wagner <dwagner@suse.de>
Cc: Hannes Reinecke <hare@suse.de>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH blktests v1] nvme/045: test queue count changes on reconnect
Date: Wed, 31 Aug 2022 12:44:20 +0000 [thread overview]
Message-ID: <a135eef8-ee5a-fdc9-c8c3-f591b3fa0d2e@nvidia.com> (raw)
In-Reply-To: <20220831120900.13129-1-dwagner@suse.de>
On 8/31/22 05:09, Daniel Wagner wrote:
> The target is allowed to change the number of I/O queues. Test if the
> host is able to reconnect in this scenario.
>
> This test depends that the target supporting setting the amount of I/O
> queues via attr_qid_max configfs file. If this not the case, the test
> will always pass. Unfortunatly, we can't test if the file exist before
> creating a subsystem.
Perhaps create a subsystem and skip the test instead of passing with
right skip reason since it creates ?
OR that is too complicated to implement in the test ?
-ck
next prev parent reply other threads:[~2022-08-31 12:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 12:09 [PATCH blktests v1] nvme/045: test queue count changes on reconnect Daniel Wagner
2022-08-31 12:44 ` Chaitanya Kulkarni [this message]
2022-08-31 12:51 ` 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=a135eef8-ee5a-fdc9-c8c3-f591b3fa0d2e@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
/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