From: Chao Leng <lengchao@huawei.com>
To: Keith Busch <kbusch@kernel.org>
Cc: Hannes Reinecke <hare@suse.de>, <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH] nvme-rdma: fix crash for no IO queues
Date: Wed, 3 Mar 2021 11:39:11 +0800 [thread overview]
Message-ID: <1fc0b92d-0726-9309-42ce-3e64858cd3aa@huawei.com> (raw)
In-Reply-To: <20210303031416.GD22346@redsun51.ssa.fujisawa.hgst.com>
On 2021/3/3 11:14, Keith Busch wrote:
> On Wed, Mar 03, 2021 at 10:27:01AM +0800, Chao Leng wrote:
>> On 2021/3/3 2:24, Keith Busch wrote:
>>> We can continue to administrate a controller that didn't create IO
>>> queues, but the controller must provide a response to all commands. If
>>> it doesn't, the controller will either be reset or abandoned. This
>>> should be the same behavior for any transport, though; there's nothing
>>> special about PCIe for that.
>> Though I don't see any useful scenarios for nvme over fabric now,
>> Reserved for future possibilities may be a better choice.
>
> The admin queue may be the only way for a user to retrieve useful
> information on the malfunctioning controller. The telemetry log isn't
> unique to PCIe.
User can also directly visit target to get these information for
nvme over fabrics.
> .
>
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-03-03 14:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 7:26 [PATCH] nvme-rdma: fix crash for no IO queues Chao Leng
2021-02-23 22:03 ` Chaitanya Kulkarni
2021-02-24 5:52 ` Chao Leng
2021-02-23 23:21 ` Keith Busch
2021-02-24 5:59 ` Chao Leng
2021-02-27 9:12 ` Hannes Reinecke
2021-02-27 9:30 ` Chao Leng
2021-03-02 7:48 ` Hannes Reinecke
2021-03-02 9:49 ` Chao Leng
2021-03-02 18:24 ` Keith Busch
2021-03-03 2:27 ` Chao Leng
2021-03-03 3:14 ` Keith Busch
2021-03-03 3:39 ` Chao Leng [this message]
2021-03-03 7:41 ` Hannes Reinecke
2021-03-03 15:08 ` Keith Busch
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=1fc0b92d-0726-9309-42ce-3e64858cd3aa@huawei.com \
--to=lengchao@huawei.com \
--cc=hare@suse.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.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