nvmet/nvmet_fc: add events for discovery controller rescan
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest7 patches 0 repliesNew
- v17 patches 0 repliesSuperseded
Changes in v2 from the cover letter
Revise lpfc patch 6 to check for port role nvme discovery not just
nvme target
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/7 | nvmet: add transport discovery change opdrivers/ drivers/ drivers/ | +8 | 1 reply | |
| 1/7 | nvmet: add transport discovery change op | +0 | 1 reply | |
| 1/7 | nvmet: add transport discovery change op | +0 | 1 reply | |
| 2/7 | nvmet_fc: add transport discovery change event callback supportdrivers/ include/ | +17 | 0 replies | |
| 3/7 | nvme-fcloop: Add support for nvmet discovery_event opdrivers/ | +37 | 0 replies | |
| 4/7 | lpfc: Add support to generate RSCN events for nportdrivers/ drivers/ drivers/ +3 more | +163 | 0 replies | |
| 5/7 | lpfc: add nvmet discovery_event op supportdrivers/ | +17 | 0 replies | |
| 6/7 | lpfc: Add support for translating an RSCN rcv into a discovery rescandrivers/ drivers/ drivers/ | +51 | 0 replies | |
| 7/7 | lpfc: Add sysfs interface to post NVME RSCNdrivers/ drivers/ | +61 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCH v2 0/7] nvmet/nvmet_fc: add events for discovery controller rescan
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(+)
Signature · 1 line
2.13.7