From: James Smart <jsmart2021@gmail.com>
To: linux-scsi@vger.kernel.org
Cc: James Smart <jsmart2021@gmail.com>
Subject: [PATCH 0/5] nvmet/nvmet_fc: add events for discovery controller rescan
Date: Sat, 28 Oct 2017 18:14:51 -0700 [thread overview]
Message-ID: <20171029011456.12885-1-jsmart2021@gmail.com> (raw)
Note: These patches were posted to the nvme list this morning. I should
have cc'd the scsi list as well - so I'm not posting to the scsi list.
I fully expect all patches to be pulled via the nvme-4.15 tree then the
block tree.
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
next reply other threads:[~2017-10-29 1:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 1:14 James Smart [this message]
2017-10-29 1:14 ` [PATCH 1/5] nvmet: call transport on subsystem add and delete James Smart
2017-10-29 1:14 ` [PATCH 2/5] nvmet_fc: support transport subsystem events James Smart
2017-10-29 1:14 ` [PATCH 3/5] lpfc: Add support to generate RSCN events for nport James Smart
2017-10-29 1:14 ` [PATCH 4/5] lpfc: Add NVME rescan support via RSCNs James Smart
2017-10-29 1:14 ` [PATCH 5/5] lpfc: Add sysfs interface to post NVME RSCN James Smart
2017-10-31 12:22 ` [PATCH 0/5] nvmet/nvmet_fc: add events for discovery controller rescan 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=20171029011456.12885-1-jsmart2021@gmail.com \
--to=jsmart2021@gmail.com \
--cc=linux-scsi@vger.kernel.org \
/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).