Lines Matching full:nvme
14 * ********************** FC-NVME LS API ********************
16 * Data structures used by both FC-NVME hosts and FC-NVME
17 * targets to perform FC-NVME LS requests or transmit
25 * to the LLDD to perform a NVME-FC LS request and obtain
27 * Used by nvme-fc transport (host) to send LS's such as
71 * to request the transmit the NVME-FC LS response to a
72 * NVME-FC LS request. The structure originates in the LLDD
75 * FC exchange context for the NVME-FC LS request that was
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.
132 * ********************** LLDD FC-NVME Host API ********************
134 * For FC LLDD's that are the NVME Host role.
142 * data element used during NVME Host role
148 * @port_role: What NVME roles are supported (see FC_PORT_ROLE_xxx)
172 * struct nvmefc_fcp_req - Request structure passed from NVME-FC transport
173 * to LLDD in order to perform a NVME FCP IO operation.
175 * Values set by the NVME-FC layer prior to calling the LLDD fcp_io
188 * @sqid: The nvme SQID the command is being issued on
205 * NOT a reflection of the NVME CQE completion status. Only the
206 * status of the FCP operation at the NVME-FC level.
253 * struct nvme_fc_local_port - structure used between NVME-FC transport and
254 * a LLDD to reference a local NVME host port.
260 * @port_num: NVME-FC transport host port number
261 * @port_role: NVME roles are supported on the port (see FC_PORT_ROLE_xxx)
296 * struct nvme_fc_remote_port - structure used between NVME-FC transport and
297 * a LLDD to reference a remote NVME subsystem port.
303 * @port_num: NVME-FC transport remote subsystem port number
304 * @port_role: NVME roles are supported on the port (see FC_PORT_ROLE_xxx)
307 * @localport: pointer to the NVME-FC local host port the subsystem is
341 * operational parameters for an LLDD that supports NVME host
343 * NVME-FC transport remembers template reference and may
384 * @ls_req: Called to issue a FC-NVME FC-4 LS service request.
392 * @fcp_io: called to issue a FC-NVME I/O request. The I/O may be for
394 * fully describe the io: the buffer containing the FC-NVME CMD IU
396 * and the buffer to place the FC-NVME RSP IU into. The LLDD will
415 * @xmt_ls_rsp: Called to transmit the response to a FC-NVME FC-4 LS service.
448 * memory that it would like fc nvme layer to allocate on the LLDD's
455 * memory that it would like fc nvme layer to allocate on the LLDD's
462 * memory that it would like fc nvme layer to allocate on the LLDD's
469 * memory that it would like fc nvme layer to allocate on the LLDD's
540 * Routine called to pass a NVME-FC LS request, received by the lldd,
541 * to the nvme-fc transport.
573 * @req: IO request from nvme fc to driver
578 * *************** LLDD FC-NVME Target/Subsystem API ***************
580 * For FC LLDD's that are the NVME Subsystem role
587 * data element used during NVME Subsystem role
605 /* Operations that NVME-FC layer may request the LLDD to perform for FCP */
618 * the specific FC-NVME IU operation(s) to perform
619 * for a FC-NVME FCP IO.
622 * context for a FC-NVME FCP I/O operation (e.g. a nvme sqe, the sqe-related
631 * the FCP I/O was received on, the remote FC NVME initiator that sent the
657 * @timeout: amount of time, in seconds, to wait for a response from the NVME
726 * struct nvmet_fc_target_port - structure used between NVME-FC transport and
727 * a LLDD to reference a local NVME subsystem port.
733 * @port_num: NVME-FC transport subsystem port number
765 * and operational parameters for an LLDD that supports NVME
767 * registrations. NVME-FC transport remembers template
778 * @xmt_ls_rsp: Called to transmit the response to a FC-NVME FC-4 LS service.
806 * more FC sequences (preferrably 1). Note: the fc-nvme layer
813 * Note: the FC-NVME layer may call the WRITEDATA operation
827 * may retramsit the FCP_RSP iu if necessary per FC-NVME. Upon
836 * FCP_RSP iu if FCP_CONF is not received per FC-NVME. Upon
851 * operations, the fc-nvme layer may immediate convert, in the same
880 * begun processing of a previously received NVME CMD IU. The LLDD
886 * change notifications to NVME initiators. The RSCN notifications
890 * @ls_req: Called to issue a FC-NVME FC-4 LS service request.
896 * transport is only allowed to issue FC-NVME LS's on behalf of an
946 * memory that it would like fc nvme layer to allocate on the LLDD's
1000 * Routine called to pass a NVME-FC LS request, received by the lldd,
1029 * connectivity to a NVME-FC host port which there had been active
1030 * NVMe controllers for. The host port is indicated by the
1032 * when a NVME LS was received, typically to create a new association.