Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: jthumshirn@suse.de (Johannes Thumshirn)
Subject: [PATCH 0/2] nvme_fc: add uevent to allow dynamic connects
Date: Mon, 8 May 2017 13:11:49 +0200	[thread overview]
Message-ID: <2340db12-7f96-1d05-de6a-f36ddb913e4f@suse.de> (raw)
In-Reply-To: <20170505231335.31726-1-jsmart2021@gmail.com>

On 05/06/2017 01:13 AM, jsmart2021@gmail.com wrote:
> From: James Smart <jsmart2021 at gmail.com>
> 
> These patches add support for generating a uevent which can be
> caugth and converted to a nvme-cli connect-all request for the
> FC initiator and target ports.

IMHO this should be a bit more generic. We do have two fabrics, FC and
RDMA (we can leave out PCIe here I think). *Iff* we want to do this we
at least need to do this for FC _and_ RDMA.


-- 
Johannes Thumshirn                                          Storage
jthumshirn at suse.de                                +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850

  parent reply	other threads:[~2017-05-08 11:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05 23:13 [PATCH 0/2] nvme_fc: add uevent to allow dynamic connects jsmart2021
2017-05-05 23:13 ` [PATCH 1/2] nvme_fc: create fc class and transport device jsmart2021
2017-05-05 23:13 ` [PATCH 2/2] nvme_fc: add uevent for auto-connect jsmart2021
2017-05-08 11:17   ` Hannes Reinecke
2017-05-08 18:17     ` James Smart
2017-05-08 11:11 ` Johannes Thumshirn [this message]
2017-05-08 17:22   ` [PATCH 0/2] nvme_fc: add uevent to allow dynamic connects James Smart

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=2340db12-7f96-1d05-de6a-f36ddb913e4f@suse.de \
    --to=jthumshirn@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox