From: jsmart2021@gmail.com (James Smart)
Subject: [PATCH v2 0/7] nvmet/nvmet_fc: add events for discovery controller rescan
Date: Tue, 14 May 2019 14:58:01 -0700 [thread overview]
Message-ID: <20190514215808.10572-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 rescan to the discovery controller.
FC is such a transport. RSCNs may be generated by the subsystem's FC
port and sent to the initiator or fabric controller. If a fabric, the
fabric controller will broadcast the RSCN to registered hosts. A host,
upon receiving the RSCN, would validate connectivity then initiate a
discovery controller rescan.
These patches:
- Modify the nvmet core layer to call a transport callback whenever
a port discovery change occurs. To facilitate the callback and
avoid new routines between core. and discovery.c the port structure
now has a copy of the transport ops structure.
- Modify the nvmet-fc transport to support the nvmet callback, and add
its own internal lldd api to request the lldd to generate an RSCN.
- Update nvme-fcloop test harness to support the lldd api and invoke
the rescan on the host.
- Modify the lpfc driver to support the new interfaces:
- Adds a new routine to transmit an RSCN to the other port (pt2pt)
or fabric controller. Add recognition for receipt of an RSCN.
- Add support for the nvmet lldd api for discovery event, which
invokes the RSCN transmit.
- Ties into the RSCN receipt and requests the nvme_fc transport
to rescan the remote port (discovery event will be posted).
- Adds a sysfs routine to enable manual generation of an RSCN.
v2:
Revise lpfc patch 6 to check for port role nvme discovery not just
nvme target
James Smart (7):
nvmet: add transport discovery change op
nvmet_fc: add transport discovery change event callback support
nvme-fcloop: Add support for nvmet discovery_event op
lpfc: Add support to generate RSCN events for nport
lpfc: add nvmet discovery_event op support
lpfc: Add support for translating an RSCN rcv into a discovery rescan
lpfc: Add sysfs interface to post NVME RSCN
drivers/nvme/target/core.c | 2 +
drivers/nvme/target/discovery.c | 4 ++
drivers/nvme/target/fc.c | 11 ++++
drivers/nvme/target/fcloop.c | 37 ++++++++++++
drivers/nvme/target/nvmet.h | 2 +
drivers/scsi/lpfc/lpfc.h | 2 +
drivers/scsi/lpfc/lpfc_attr.c | 60 ++++++++++++++++++
drivers/scsi/lpfc/lpfc_crtn.h | 4 ++
drivers/scsi/lpfc/lpfc_els.c | 127 +++++++++++++++++++++++++++++++++++++++
drivers/scsi/lpfc/lpfc_hbadisc.c | 35 +++++++++++
drivers/scsi/lpfc/lpfc_hw.h | 2 +
drivers/scsi/lpfc/lpfc_nvme.c | 44 ++++++++++++++
drivers/scsi/lpfc/lpfc_nvmet.c | 17 ++++++
drivers/scsi/lpfc/lpfc_sli.c | 1 +
include/linux/nvme-fc-driver.h | 6 ++
15 files changed, 354 insertions(+)
--
2.13.7
next reply other threads:[~2019-05-14 21:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 21:58 James Smart [this message]
2019-05-14 21:58 ` [PATCH v2 1/7] nvmet: add transport discovery change op James Smart
2019-05-29 22:21 ` Sagi Grimberg
2019-05-29 22:27 ` James Smart
2019-05-29 22:42 ` Sagi Grimberg
2019-05-29 22:58 ` James Smart
2019-05-30 1:04 ` Sagi Grimberg
2019-05-14 21:58 ` [PATCH v2 2/7] nvmet_fc: add transport discovery change event callback support James Smart
2019-05-14 21:58 ` [PATCH v2 3/7] nvme-fcloop: Add support for nvmet discovery_event op James Smart
2019-05-14 21:58 ` [PATCH v2 4/7] lpfc: Add support to generate RSCN events for nport James Smart
2019-05-14 21:58 ` [PATCH v2 5/7] lpfc: add nvmet discovery_event op support James Smart
2019-05-14 21:58 ` [PATCH v2 6/7] lpfc: Add support for translating an RSCN rcv into a discovery rescan James Smart
2019-05-14 21:58 ` [PATCH v2 7/7] lpfc: Add sysfs interface to post NVME RSCN James Smart
2019-05-29 23:12 ` [PATCH v2 0/7] nvmet/nvmet_fc: add events for discovery controller rescan Arun Easi
2019-05-30 18:04 ` 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=20190514215808.10572-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.