All of lore.kernel.org
 help / color / mirror / Atom feed
From: jsmart2021@gmail.com (James Smart)
Subject: [PATCH 0/5] nvmet/nvmet_fc: add events for discovery controller rescan
Date: Sat, 28 Oct 2017 10:21:09 -0700	[thread overview]
Message-ID: <20171028172114.2045-1-jsmart2021@gmail.com> (raw)

A transport may have a transport-specific mechanism that can signal
when discovery controller content has changed and request a host
to reconnect to the discovery controller.

FC is such a transport. RSCNs may be generated by the FC port with
the discovery server, with the RSCNs then broadcast to the FC-NVME
hosts. A host, upon receiving the RSCN, would validate connectivity
then initiate a discovery controller rescan, allowing new subsystems
to be connected to or updating subsystem connectivity tables.

These patches:
- Modify the nvmet core layer to call a transport callback on every
  subsystem add or remove from a transport port.
- Modify the nvmet-fc transport to support the callback, and add its
  own internal lldd api to generate RSCN's via the lldd.
- Modify the lpfc driver to send/receive RSCNs for FC-NVME: transmit
  the changed attribute RSCN on the target, receiving the RSCN on
  the initiator and invoking the nvmet-fc transport rescan api.
  Also adds manual sysfs mechanism to generate the RSCN on the target.


Dick Kennedy (1):
  lpfc: Add sysfs interface to post NVME RSCN

James Smart (4):
  nvmet: call transport on subsystem add and delete
  nvmet_fc: support transport subsystem events
  lpfc: Add support to generate RSCN events for nport
  lpfc: Add NVME rescan support via RSCNs

 drivers/nvme/target/configfs.c   |   2 +
 drivers/nvme/target/core.c       |  10 ++++
 drivers/nvme/target/fc.c         |  10 ++++
 drivers/nvme/target/nvmet.h      |   2 +
 drivers/scsi/lpfc/lpfc.h         |   2 +
 drivers/scsi/lpfc/lpfc_attr.c    |  62 ++++++++++++++++++++
 drivers/scsi/lpfc/lpfc_crtn.h    |   4 ++
 drivers/scsi/lpfc/lpfc_els.c     | 118 +++++++++++++++++++++++++++++++++++++++
 drivers/scsi/lpfc/lpfc_hbadisc.c |  35 ++++++++++++
 drivers/scsi/lpfc/lpfc_hw.h      |   9 +++
 drivers/scsi/lpfc/lpfc_nvme.c    |  42 ++++++++++++++
 drivers/scsi/lpfc/lpfc_nvmet.c   |  18 ++++++
 drivers/scsi/lpfc/lpfc_sli.c     |   1 +
 include/linux/nvme-fc-driver.h   |   6 ++
 14 files changed, 321 insertions(+)

-- 
2.13.1

             reply	other threads:[~2017-10-28 17:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-28 17:21 James Smart [this message]
2017-10-28 17:21 ` [PATCH 1/5] nvmet: call transport on subsystem add and delete James Smart
2017-10-28 17:21 ` [PATCH 2/5] nvmet_fc: support transport subsystem events James Smart
2017-10-28 17:21 ` [PATCH 3/5] lpfc: Add support to generate RSCN events for nport James Smart
2017-10-28 17:21 ` [PATCH 4/5] lpfc: Add NVME rescan support via RSCNs James Smart
2017-10-28 17:21 ` [PATCH 5/5] lpfc: Add sysfs interface to post NVME RSCN James Smart
2017-11-02 20:09   ` Ewan D. Milne
2017-11-02 22:02     ` James Smart
2017-10-29 16:11 ` [PATCH 0/5] nvmet/nvmet_fc: add events for discovery controller rescan Sagi Grimberg
2017-10-30  4:43   ` James Smart
2017-11-01 15:38     ` Christoph Hellwig
2017-11-01 16:03       ` James Smart
2017-11-01 16:28         ` Christoph Hellwig
2017-11-01 15:36 ` Christoph Hellwig
2017-11-01 15:55   ` James Smart
2017-11-01 15:57     ` Christoph Hellwig
2017-11-01 16:12       ` James Smart
2017-11-01 16:29         ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2017-10-29  1:14 James Smart
2017-10-31 12:22 ` Martin K. Petersen
2017-10-31 12:22   ` Martin K. Petersen

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=20171028172114.2045-1-jsmart2021@gmail.com \
    --to=jsmart2021@gmail.com \
    /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.