History

nvmet-fc: add transport discovery change event callback support

This patch adds support for the nvmet discovery_change transport op. In turn, the transport adds it's own LLDD api callback discovery_event op to request the LLDD to generate an RSCN for the discovery change.

James Smart committed 7 years ago

Commit 150d71f1 parent 9d09dd82 files · +17 −0Browse files

Unified · Split

2 files
  1. drivers/nvme/target/fc.c +11 −0
  2. include/linux/nvme-fc-driver.h +6 −0
drivers/nvme/target/fc.c+11−0
@@ -2549,6 +2549,16 @@ nvmet_fc_remove_port(struct nvmet_port *port) · 2548 unmodified lines
2549 kfree(pe);2549 kfree(pe);
2550}2550}
2551 2551
2552static void
2553nvmet_fc_discovery_chg(struct nvmet_port *port)
2554{
2555 struct nvmet_fc_port_entry *pe = port->priv;
2556 struct nvmet_fc_tgtport *tgtport = pe->tgtport;
2557
2558 if (tgtport && tgtport->ops->discovery_event)
2559 tgtport->ops->discovery_event(&tgtport->fc_target_port);
2560}
2561
2552static const struct nvmet_fabrics_ops nvmet_fc_tgt_fcp_ops = {2562static const struct nvmet_fabrics_ops nvmet_fc_tgt_fcp_ops = {
2553 .owner = THIS_MODULE,2563 .owner = THIS_MODULE,
2554 .type = NVMF_TRTYPE_FC,2564 .type = NVMF_TRTYPE_FC,
@@ -2557,6 +2567,7 @@ static const struct nvmet_fabrics_ops nvmet_fc_tgt_fcp_ops = { · 2 unmodified lines
2557 .remove_port = nvmet_fc_remove_port,2567 .remove_port = nvmet_fc_remove_port,
2558 .queue_response = nvmet_fc_fcp_nvme_cmd_done,2568 .queue_response = nvmet_fc_fcp_nvme_cmd_done,
2559 .delete_ctrl = nvmet_fc_delete_ctrl,2569 .delete_ctrl = nvmet_fc_delete_ctrl,
2570 .discovery_chg = nvmet_fc_discovery_chg,
2560};2571};
2561 2572
2562static int __init nvmet_fc_init_module(void)2573static int __init nvmet_fc_init_module(void)
include/linux/nvme-fc-driver.h+6−0
@@ -791,6 +791,11 @@ struct nvmet_fc_target_port { · 790 unmodified lines
791 * nvmefc_tgt_fcp_req.791 * nvmefc_tgt_fcp_req.
792 * Entrypoint is Optional.792 * Entrypoint is Optional.
793 *793 *
794 * @discovery_event: Called by the transport to generate an RSCN
795 * change notifications to NVME initiators. The RSCN notifications
796 * should cause the initiator to rescan the discovery controller
797 * on the targetport.
798 *
794 * @max_hw_queues: indicates the maximum number of hw queues the LLDD799 * @max_hw_queues: indicates the maximum number of hw queues the LLDD
795 * supports for cpu affinitization.800 * supports for cpu affinitization.
796 * Value is Mandatory. Must be at least 1.801 * Value is Mandatory. Must be at least 1.
@@ -832,6 +837,7 @@ struct nvmet_fc_target_template { · 35 unmodified lines
832 struct nvmefc_tgt_fcp_req *fcpreq);837 struct nvmefc_tgt_fcp_req *fcpreq);
833 void (*defer_rcv)(struct nvmet_fc_target_port *tgtport,838 void (*defer_rcv)(struct nvmet_fc_target_port *tgtport,
834 struct nvmefc_tgt_fcp_req *fcpreq);839 struct nvmefc_tgt_fcp_req *fcpreq);
840 void (*discovery_event)(struct nvmet_fc_target_port *tgtport);
835 841
836 u32 max_hw_queues;842 u32 max_hw_queues;
837 u16 max_sgl_segments;843 u16 max_sgl_segments;

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t