From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH v2 0/3] Support discovery log change events
Date: Wed, 31 Jul 2019 18:32:05 -0700 [thread overview]
Message-ID: <53ec841c-f71e-1789-1f7c-7ae3a0aa2d66@grimberg.me> (raw)
In-Reply-To: <20190712180211.26333-1-sagi@grimberg.me>
> We want to be able to support discovery log change events automatically
> without user intervention.
>
> The definition of discovery log change events applies on "persistent" long
> lived controllers, so first we need to have discovery controllers to stay
> for a long time and accept kato value.
>
> Then when we do happen to get a discovery log change event on the persistent
> discovery controller, we simply fire a udev event to user-space to re-query
> the discovery log page and connect to new subsystems in the fabric.
>
> This works with James' latest nvme-cli patches.
James, I've applied this to nvme-5.4
Are you sending out the nvme-cli part? If you can make sure
that it works with what is in nvme-5.4 it will be great..
Thanks
prev parent reply other threads:[~2019-08-01 1:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 18:02 [PATCH v2 0/3] Support discovery log change events Sagi Grimberg
2019-07-12 18:02 ` [PATCH v2 1/3] nvme-fabrics: allow discovery subsystems accept a kato Sagi Grimberg
2019-07-14 8:08 ` Minwoo Im
2019-07-14 15:00 ` James Smart
2019-07-19 13:48 ` Hannes Reinecke
2019-07-12 18:02 ` [PATCH v2 2/3] nvme: enable aen also for discovery controllers Sagi Grimberg
2019-07-14 8:09 ` Minwoo Im
2019-07-14 15:04 ` James Smart
2019-07-19 13:49 ` Hannes Reinecke
2019-07-12 18:02 ` [PATCH v2 3/3] nvme: fire discovery log page change events to userspace Sagi Grimberg
2019-07-14 8:14 ` Minwoo Im
2019-07-14 15:13 ` James Smart
2019-07-19 13:49 ` Hannes Reinecke
[not found] ` <20190822002328.GP9511@lst.de>
[not found] ` <205d06ab-fedc-739d-323f-b358aff2cbfe@grimberg.me>
[not found] ` <e4603511-6dae-e26d-12a9-e9fa727a8d03@grimberg.me>
[not found] ` <20190826065639.GA11036@lst.de>
[not found] ` <20190826075916.GA30396@kroah.com>
[not found] ` <ac168168-fed2-2b57-493e-e88261ead73b@grimberg.me>
[not found] ` <20190830055514.GC8492@lst.de>
2019-08-30 18:08 ` Sagi Grimberg
2019-08-30 18:36 ` James Smart
2019-08-30 21:07 ` Sagi Grimberg
2019-08-30 22:24 ` James Smart
2019-09-09 15:10 ` Hannes Reinecke
[not found] ` <20190830062036.GA15257@kroah.com>
2019-08-30 18:14 ` Sagi Grimberg
2019-09-02 19:33 ` Greg Kroah-Hartman
2019-09-04 1:35 ` Sagi Grimberg
2019-09-04 5:25 ` Greg Kroah-Hartman
2019-08-01 1:32 ` Sagi Grimberg [this message]
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=53ec841c-f71e-1789-1f7c-7ae3a0aa2d66@grimberg.me \
--to=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;
as well as URLs for NNTP newsgroup(s).