From: Sagi Grimberg <sagi@grimberg.me>
To: Daniel Wagner <dwagner@suse.de>, linux-nvme@lists.infradead.org
Cc: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: Re: [PATCH v2] nvmet: force reconnect when number of queue changes
Date: Wed, 28 Sep 2022 09:55:11 +0300 [thread overview]
Message-ID: <d151b0c1-d28e-faeb-03d4-ed28b9768ee2@grimberg.me> (raw)
In-Reply-To: <20220927143157.3659-1-dwagner@suse.de>
> In order to be able to test queue number changes we need to make sure
> that the host reconnects.
>
> The initial idea was to disable and re-enable the ports and have the
> host to wait until the KATO timer expires and enter error
> recovery. But in this scenario the host could see DNR for a connection
> attempt which results in the host dropping the connection completely.
>
> We can force to reconnect the host by deleting all controllers
> connected to subsystem, which results the host observing a failing
> command and tries to reconnect.
This looks like a change that attempts to fix a host issue from the
target side... Why do we want to do that?
next prev parent reply other threads:[~2022-09-28 6:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 14:31 [PATCH v2] nvmet: force reconnect when number of queue changes Daniel Wagner
2022-09-27 15:01 ` Daniel Wagner
2022-09-28 6:55 ` Sagi Grimberg [this message]
2022-09-28 7:48 ` Daniel Wagner
2022-09-28 8:31 ` Sagi Grimberg
2022-09-28 9:02 ` Daniel Wagner
2022-09-28 12:39 ` Knight, Frederick
2022-09-28 13:50 ` Daniel Wagner
2022-09-28 14:23 ` Sagi Grimberg
2022-09-28 15:21 ` Hannes Reinecke
2022-09-28 16:01 ` Knight, Frederick
2022-10-05 18:15 ` Daniel Wagner
2022-10-06 11:37 ` Sagi Grimberg
2022-10-06 20:15 ` James Smart
2022-10-06 20:54 ` Knight, Frederick
2022-09-28 16:01 ` Knight, Frederick
2022-09-28 15:01 ` John Meneghini
2022-09-28 15:26 ` Daniel Wagner
2022-09-28 18:02 ` Knight, Frederick
2022-09-29 2:14 ` John Meneghini
2022-09-29 3:04 ` Knight, Frederick
2022-09-30 7:03 ` Hannes Reinecke
2022-09-30 6:32 ` Hannes Reinecke
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=d151b0c1-d28e-faeb-03d4-ed28b9768ee2@grimberg.me \
--to=sagi@grimberg.me \
--cc=dwagner@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).