Lines Matching full:transport
23 * struct nvmefc_ls_req - Request structure passed from the transport
26 * Used by nvme-fc transport (host) to send LS's such as
29 * Used by the nvmet-fc transport (controller) to send
69 * struct nvmefc_ls_rsp - Structure passed from the transport to the LLDD
72 * and is given to the transport via the xxx_rcv_ls_req()
73 * transport routine. As such, the structure represents the
76 * Used by the LLDD to pass the nvmet-fc transport (controller)
79 * Used by the LLDD to pass the nvme-fc transport (host)
85 * or nvme-fc layer via the xxx_rcv_ls_req() transport routines.
92 * address of the structure back to the transport LS rsp done() routine,
93 * allowing the transport release dma resources. Upon completion of
95 * the transport and the LLDD can de-allocate the structure.
102 * transport layer will fully set the fields in order to specify the
104 * to be called upon completion of the transmit. The transport layer
107 * Values set by the transport layer prior to calling the LLDD xmt_ls_rsp
115 * @nvme_fc_private: pointer to an internal transport-specific structure
116 * used as part of the transport done() processing. The LLDD is
171 * struct nvmefc_fcp_req - Request structure passed from NVME-FC transport
252 * struct nvme_fc_local_port - structure used between NVME-FC transport and
255 * transport interface.
259 * @port_num: NVME-FC transport host port number
295 * struct nvme_fc_remote_port - structure used between NVME-FC transport and
298 * transport interface.
302 * @port_num: NVME-FC transport remote subsystem port number
342 * NVME-FC transport remembers template reference and may
345 * Host/Initiator Transport Entrypoints/Parameters:
397 * any transport error, and call the "done" routine specified in the
405 * indicating an FC transport Aborted status.
411 * indicating an FC transport Aborted status.
538 * to the nvme-fc transport.
541 * transport.
542 * If the return value is non-zero: the transport has not accepted the
545 * Note: if the LLDD receives and ABTS for the LS prior to the transport
552 * Note: if an RCV LS was successfully posted to the transport and the
554 * the lsrsp structure, the transport will still call xmt_ls_rsp()
714 * struct nvmet_fc_target_port - structure used between NVME-FC transport and
717 * transport interface.
721 * @port_num: NVME-FC transport subsytem port number
755 * registrations. NVME-FC transport remembers template
758 * Subsystem/Target Transport Entrypoints/Parameters:
778 * The transport will always call the xmt_ls_rsp() routine for any
831 * transport calls the fcp_req_release() callback to return ownership
845 * @fcp_abort: Called by the transport to abort an active command.
851 * fcp_abort() callback completes, the transport will wait for any
857 * @fcp_req_release: Called by the transport to return a nvmefc_tgt_fcp_req
863 * @defer_rcv: Called by the transport to signal the LLLD that it has
869 * @discovery_event: Called by the transport to generate an RSCN
880 * transport is only allowed to issue FC-NVME LS's on behalf of an
884 * was delivered to the transport. The transport will save the
888 * the remote port in the transport.
898 * indicating an FC transport Aborted status.
985 * to the nvmet-fc transport.
988 * transport.
989 * If the return value is non-zero: the transport has not accepted the
992 * Note: if the LLDD receives and ABTS for the LS prior to the transport
999 * Note: if an RCV LS was successfully posted to the transport and the
1001 * the lsrsp structure, the transport will still call xmt_ls_rsp()
1015 * hosthandle. The hosthandle is given to the nvmet-fc transport
1017 * The nvmet-fc transport will cache the hostport value with the
1019 * When the LLDD calls this routine, the nvmet-fc transport will
1023 * must assume the transport may subsequently utilize hosthandle as
1027 * port, the nvmet-fc transport will call the ops->host_release()
1028 * callback. As of the callback, the nvmet-fc transport will no
1035 * If nvmet_fc_rcv_fcp_req returns non-zero, the transport has not accepted