From: James Smart <jsmart2021@gmail.com>
To: Sagi Grimberg <sagi@grimberg.me>, linux-nvme@lists.infradead.org
Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
Martin Belanger <nitram_67@hotmail.com>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH rfc 0/1] Fix missing AENs when discovery controllers are disconnected
Date: Sat, 10 Sep 2022 08:47:23 -0700 [thread overview]
Message-ID: <9eb798de-149d-a56d-ac00-dd6b7ae79a81@gmail.com> (raw)
In-Reply-To: <20220907142411.101950-1-sagi@grimberg.me>
On 9/7/2022 7:24 AM, Sagi Grimberg wrote:
> When a discovery controller is disconnected, no AENs will
> arrive to notify the host about discovery log-page changes.
>
> This attempts to fix it with a new connection parameter asking
> the kernel to send a dedicated udev event for this case. Prior
> attempt tried to use "connected" event already sent by the kernel
> however this also applied on the first connected, causing undesired
> side-effects when issuing a simple 'discover' command.
>
> The patchset includes the nvme-cli/libnvme counter-parts as well.
Sagi,
Do we really need another parameter/option ? seems awkward to need
userspace to figure it out.
The transport certainly knows the difference between 1st time connect
and nth time re-connect - perhaps this should be a simple flag on the
nvme ctrl struct set by the transport ? Simple thing for rdma/tcp to
set flag at end of successful xxx_create_ctrl(), while FC, given it does
reconnects w/o a first successful connect needs a little more logic.
-- james
next prev parent reply other threads:[~2022-09-10 15:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 14:24 [PATCH rfc 0/1] Fix missing AENs when discovery controllers are disconnected Sagi Grimberg
2022-09-07 14:24 ` [PATCH rfc 1/1] fabrics: support notify_rediscover connect parameter Sagi Grimberg
2022-09-07 14:24 ` [PATCH libnvme 2/1] nvme: Add generic connect parameter support detection Sagi Grimberg
2022-09-09 6:56 ` Daniel Wagner
2022-09-12 12:32 ` Sagi Grimberg
2022-09-12 14:19 ` Daniel Wagner
2022-09-07 14:24 ` [PATCH libnvme 3/1] fabrics: add notify_rediscover parameter Sagi Grimberg
2022-09-09 6:58 ` Daniel Wagner
2022-09-12 12:33 ` Sagi Grimberg
2022-09-12 14:42 ` Daniel Wagner
2022-09-07 14:24 ` [PATCH nvme-cli 4/1] fabrics: re-read the discovery log page when a discovery controller reconnected Sagi Grimberg
2022-09-10 15:47 ` James Smart [this message]
2022-09-12 12:39 ` [PATCH rfc 0/1] Fix missing AENs when discovery controllers are disconnected Sagi Grimberg
2022-09-13 0:06 ` James Smart
2022-09-14 10:29 ` Sagi Grimberg
2022-09-14 15:00 ` James Smart
2022-09-14 15:31 ` Sagi Grimberg
2022-09-14 17:26 ` James Smart
2022-09-18 14:12 ` Sagi Grimberg
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=9eb798de-149d-a56d-ac00-dd6b7ae79a81@gmail.com \
--to=jsmart2021@gmail.com \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nitram_67@hotmail.com \
--cc=sagi@grimberg.me \
/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