include/linux/nvme-fc-driver.h

24  * struct nvmefc_ls_req - Request structure passed from the transport
27  *            Used by nvme-fc transport (host) to send LS's such as
30  *            Used by the nvmet-fc transport (controller) to send
70  * struct nvmefc_ls_rsp - Structure passed from the transport to the LLDD
73  *            and is given to the transport via the xxx_rcv_ls_req()
74  *            transport routine. As such, the structure represents the
77  *            Used by the LLDD to pass the nvmet-fc transport (controller)
80  *            Used by the LLDD to pass the nvme-fc transport (host)
86  * or nvme-fc layer via the xxx_rcv_ls_req() transport routines.
93  * address of the structure back to the transport LS rsp done() routine,
94  * allowing the transport release dma resources. Upon completion of
96  * the transport and the LLDD can de-allocate the structure.
103  *     transport layer will fully set the fields in order to specify the
105  *     to be called upon completion of the transmit.  The transport layer
108  * Values set by the transport layer prior to calling the LLDD xmt_ls_rsp
116  * @nvme_fc_private:  pointer to an internal transport-specific structure
117  *            used as part of the transport done() processing. The LLDD is
172  * struct nvmefc_fcp_req - Request structure passed from NVME-FC transport
253  * struct nvme_fc_local_port - structure used between NVME-FC transport and
256  *                 transport interface.
260  * @port_num:  NVME-FC transport host port number
296  * struct nvme_fc_remote_port - structure used between NVME-FC transport and
299  *                 transport interface.
303  * @port_num:  NVME-FC transport remote subsystem port number
343  *                 NVME-FC transport remembers template reference and may
346  * Host/Initiator Transport Entrypoints/Parameters:
398  *       any transport error, and call the "done" routine specified in the
406  *       indicating an FC transport Aborted status.
412  *       indicating an FC transport Aborted status.
541  * to the nvme-fc transport.
544  *   transport.
545  * If the return value is non-zero: the transport has not accepted the
548  * Note: if the LLDD receives and ABTS for the LS prior to the transport
555  * Note: if an RCV LS was successfully posted to the transport and the
557  * the lsrsp structure, the transport will still call xmt_ls_rsp()
726  * struct nvmet_fc_target_port - structure used between NVME-FC transport and
729  *                 transport interface.
733  * @port_num:  NVME-FC transport subsystem port number
767  *                 registrations. NVME-FC transport remembers template
770  * Subsystem/Target Transport Entrypoints/Parameters:
790  *       The transport will always call the xmt_ls_rsp() routine for any
847  *       transport calls the fcp_req_release() callback to return ownership
861  * @fcp_abort:  Called by the transport to abort an active command.
867  *       fcp_abort() callback completes, the transport will wait for any
873  * @fcp_req_release:  Called by the transport to return a nvmefc_tgt_fcp_req
879  * @defer_rcv:  Called by the transport to signal the LLLD that it has
885  * @discovery_event:  Called by the transport to generate an RSCN
896  *       transport is only allowed to issue FC-NVME LS's on behalf of an
900  *       was delivered to the transport. The transport will save the
904  *       the remote port in the transport.
914  *       indicating an FC transport Aborted status.
923  * @host_traddr: called by the transport to retrieve the node name and
1005  * to the nvmet-fc transport.
1008  *   transport.
1009  * If the return value is non-zero: the transport has not accepted the
1012  * Note: if the LLDD receives and ABTS for the LS prior to the transport
1019  * Note: if an RCV LS was successfully posted to the transport and the
1021  * the lsrsp structure, the transport will still call xmt_ls_rsp()
1035  * hosthandle. The hosthandle is given to the nvmet-fc transport
1037  * The nvmet-fc transport will cache the hostport value with the
1039  * When the LLDD calls this routine, the nvmet-fc transport will
1043  * must assume the transport may subsequently utilize hosthandle as
1047  * port, the nvmet-fc transport will call the ops->host_release()
1048  * callback. As of the callback, the nvmet-fc transport will no
1055  * If nvmet_fc_rcv_fcp_req returns non-zero, the transport has not accepted