From: hare@suse.de (Hannes Reinecke)
Subject: [PATCH rfc 0/3] add support to discovery async event notifications
Date: Fri, 5 Oct 2018 07:50:05 +0200 [thread overview]
Message-ID: <cbf24fc6-a6dd-dcc4-35ce-97bec248dd32@suse.de> (raw)
In-Reply-To: <20181004212328.30205-1-sagi@grimberg.me>
On 10/4/18 11:23 PM, Sagi Grimberg wrote:
> In order to support discovery AENs we need to have two things:
> 1. Support long lived discovery controller sessions that would allow to
> receive discovery AENs. This means we need to specify kato in connect
>
> 2. Support discovery log change events. The choice here is to simply fire
> a udev event and let userspace to:
> 1. issue an updated discovery log page via our discovery controller (1)
> 2. connect to every new subsystem/port that exists in the system.
>
> This patch set was developed against the nvmet support patch set from Jay.
>
> nvme-cli patches are also included in this series.
>
> the udev rule that ultimately achieves dynamic discovery enumeration (TP 8002)
> is:
>
> SUBSYSTEM=="nvme", ACTION=="change", \
> RUN+="/usr/sbin/nvme connect-all --device=nvme$env{NVME_INSTANCE} --transport=$env{NVME_TRTYPE} \
> --traddr=$env{NVME_TRADDR} --trsvcid=$env{NVME_TRSVCID} & disown
>
Not sure that'll work; IIRC udev doesn't follow the bash syntax of '&'
here. Have you checked?
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare at suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: F. Imend?rffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG N?rnberg)
next prev parent reply other threads:[~2018-10-05 5:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 21:23 [PATCH rfc 0/3] add support to discovery async event notifications Sagi Grimberg
2018-10-04 21:23 ` [PATCH rfc 1/3] nvme-fabrics: allow discovery subsystems accept a kato Sagi Grimberg
2018-10-05 5:50 ` Hannes Reinecke
2018-10-04 21:23 ` [PATCH rfc 2/3] nvme: enable aen also for discovery controllers Sagi Grimberg
2018-10-05 5:51 ` Hannes Reinecke
2018-10-04 21:23 ` [PATCH rfc 3/3] nvme: fire discovery log page change events to userspace Sagi Grimberg
2018-10-05 5:51 ` Hannes Reinecke
2018-10-04 21:23 ` [PATCH 4/3 rfc nvme-cli] fabrics: support persistent connections to a discovery controller Sagi Grimberg
2018-10-04 21:23 ` [PATCH 5/3 rfc nvme-cli] fabrics: allow user to retrieve discovery log from existing " Sagi Grimberg
2018-10-05 5:50 ` Hannes Reinecke [this message]
2018-10-05 7:08 ` [PATCH rfc 0/3] add support to discovery async event notifications Sagi Grimberg
2018-10-05 7:36 ` Hannes Reinecke
2018-10-05 19:34 ` Sagi Grimberg
2018-10-16 1:11 ` Sagi Grimberg
2018-10-16 5:59 ` Hannes Reinecke
2018-10-16 17:59 ` James Smart
2018-10-17 15:29 ` Hannes Reinecke
2018-10-19 0:44 ` Sagi Grimberg
2018-10-19 16:09 ` James Smart
2018-10-17 0:38 ` 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=cbf24fc6-a6dd-dcc4-35ce-97bec248dd32@suse.de \
--to=hare@suse.de \
/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.