From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH 0/3 rfc] Support discovery log change events
Date: Fri, 22 Feb 2019 18:31:12 -0800 [thread overview]
Message-ID: <20190223023117.20517-1-sagi@grimberg.me> (raw)
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.
Review and feedback is welcome.
Sagi Grimberg (3):
nvme-fabrics: allow discovery subsystems accept a kato
nvme: enable aen also for discovery controllers
nvme: fire discovery log page change events to userspace
drivers/nvme/host/core.c | 37 ++++++++++++++++++++++++++++++++++---
drivers/nvme/host/fabrics.c | 12 ++----------
2 files changed, 36 insertions(+), 13 deletions(-)
--
2.17.1
next reply other threads:[~2019-02-23 2:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 2:31 Sagi Grimberg [this message]
2019-02-23 2:31 ` [PATCH 1/3 rfc] nvme-fabrics: allow discovery subsystems accept a kato Sagi Grimberg
2019-02-24 17:13 ` Hannes Reinecke
2019-02-23 2:31 ` [PATCH 2/3 rfc] nvme: enable aen also for discovery controllers Sagi Grimberg
2019-02-24 17:14 ` Hannes Reinecke
2019-02-25 0:07 ` Max Gurtovoy
2019-02-25 21:24 ` Sagi Grimberg
2019-02-23 2:31 ` [PATCH 3/3 rfc] nvme: fire discovery log page change events to userspace Sagi Grimberg
2019-02-24 17:16 ` Hannes Reinecke
2019-02-25 21:25 ` Sagi Grimberg
2019-02-23 2:31 ` [PATCH rfc nvme-cli 4/5] fabrics: support persistent connections to a discovery controller Sagi Grimberg
2019-02-23 2:34 ` Sagi Grimberg
2019-02-23 2:31 ` [PATCH rfc nvme-cli 5/5] fabrics: allow user to retrieve discovery log from existing " Sagi Grimberg
2019-02-23 2:34 ` 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=20190223023117.20517-1-sagi@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 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.