From: Hannes Reinecke <hare@suse.de>
To: "Belanger, Martin" <Martin.Belanger@dell.com>,
Sagi Grimberg <sagi@grimberg.me>,
Martin Belanger <nitram_67@hotmail.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: "kbusch@kernel.org" <kbusch@kernel.org>,
"axboe@fb.com" <axboe@fb.com>, "hch@lst.de" <hch@lst.de>
Subject: Re: [PATCH 3/4] nvme-fabrics: add tp8010 support
Date: Wed, 2 Feb 2022 09:36:29 +0100 [thread overview]
Message-ID: <4e79411d-3009-a376-6ecb-bb10100f9cee@suse.de> (raw)
In-Reply-To: <SJ0PR19MB4544AC1F430E3B025FE8D0C5F2259@SJ0PR19MB4544.namprd19.prod.outlook.com>
On 1/31/22 17:16, Belanger, Martin wrote:
>
>>> Hi Sagi. Thanks for the code snippet. I just had a question about your
>> comment.
>>>
>>> You say that you don’t see any point to send an event on the
>>> disconnect because it is async. I don’t quite understand that part.
>>> For example, I've observed that when connectivity is lost the kernel
>>> will try to connect every
>>> 10 sec. And it will keep trying to connect 60 times (i.e. 10 min)
>>> before giving up. Wouldn't sending an "offline" event when
>>> connectivity is lost give user space apps a heads up that the nvme device
>> may not respond.
>>
>> Why does userspace need it?
>>
>> When the host will disconnect it will send event asynchronously, so
>> userspace cannot reliably do anything before the host disconnects.
>> Other than that I don't understand what would userspace do with "offline -
>> I/O is going to fail"...
>
> I was just asking for completeness. Some apps may use it.
>
We had a similar discussion during udev development; originally we had
KOBJ_ONLINE and KOBJ_OFFLINE uevents
Turned out that the KOBJ_OFFLINE events were quite pointless (as Sagi
indicated), and hence we settled on a single KOBJ_CHANGE event which
typically is sent when a device/system gets back online.
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
next prev parent reply other threads:[~2022-02-02 8:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220125145956.14746-1-nitram_67@hotmail.com>
2022-01-25 14:59 ` [PATCH 1/4] nvme-fabrics: add discovery controller type Martin Belanger
2022-01-27 9:16 ` Hannes Reinecke
2022-01-27 13:37 ` Belanger, Martin
2022-01-27 13:16 ` Sagi Grimberg
2022-01-25 14:59 ` [PATCH 2/4] nvme: add host symbolic name Martin Belanger
2022-01-27 9:18 ` Hannes Reinecke
2022-01-27 13:20 ` Sagi Grimberg
2022-01-25 14:59 ` [PATCH 3/4] nvme-fabrics: add tp8010 support Martin Belanger
2022-01-27 9:30 ` Hannes Reinecke
2022-01-27 13:12 ` Sagi Grimberg
2022-01-27 13:30 ` Belanger, Martin
2022-01-27 14:28 ` Hannes Reinecke
2022-01-27 21:59 ` Sagi Grimberg
2022-01-28 17:55 ` Belanger, Martin
2022-01-28 21:49 ` Hannes Reinecke
2022-01-28 23:02 ` Belanger, Martin
2022-01-29 8:43 ` Hannes Reinecke
2022-01-29 12:23 ` Belanger, Martin
2022-01-29 12:47 ` Hannes Reinecke
2022-01-30 8:46 ` Sagi Grimberg
2022-01-30 13:18 ` Sagi Grimberg
2022-01-31 12:08 ` Belanger, Martin
2022-01-31 16:05 ` Sagi Grimberg
2022-01-31 16:16 ` Belanger, Martin
2022-01-31 18:56 ` Sagi Grimberg
2022-02-02 8:36 ` Hannes Reinecke [this message]
2022-01-31 17:03 ` John Meneghini
2022-01-31 17:17 ` Belanger, Martin
2022-01-31 18:28 ` John Meneghini
2022-01-25 14:59 ` [PATCH 4/4] nvme-fabrics: add explicit deregistration on disconnect Martin Belanger
2022-01-27 9:31 ` Hannes Reinecke
2022-01-27 13:14 ` 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=4e79411d-3009-a376-6ecb-bb10100f9cee@suse.de \
--to=hare@suse.de \
--cc=Martin.Belanger@dell.com \
--cc=axboe@fb.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.