Lines Matching full:nvme
13 * ********************** FC-NVME LS API ********************
15 * Data structures used by both FC-NVME hosts and FC-NVME
16 * targets to perform FC-NVME LS requests or transmit
24 * to the LLDD to perform a NVME-FC LS request and obtain
26 * Used by nvme-fc transport (host) to send LS's such as
70 * to request the transmit the NVME-FC LS response to a
71 * NVME-FC LS request. The structure originates in the LLDD
74 * FC exchange context for the NVME-FC LS request that was
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.
131 * ********************** LLDD FC-NVME Host API ********************
133 * For FC LLDD's that are the NVME Host role.
141 * data element used during NVME Host role
147 * @port_role: What NVME roles are supported (see FC_PORT_ROLE_xxx)
171 * struct nvmefc_fcp_req - Request structure passed from NVME-FC transport
172 * to LLDD in order to perform a NVME FCP IO operation.
174 * Values set by the NVME-FC layer prior to calling the LLDD fcp_io
187 * @sqid: The nvme SQID the command is being issued on
204 * NOT a reflection of the NVME CQE completion status. Only the
205 * status of the FCP operation at the NVME-FC level.
252 * struct nvme_fc_local_port - structure used between NVME-FC transport and
253 * a LLDD to reference a local NVME host port.
259 * @port_num: NVME-FC transport host port number
260 * @port_role: NVME roles are supported on the port (see FC_PORT_ROLE_xxx)
295 * struct nvme_fc_remote_port - structure used between NVME-FC transport and
296 * a LLDD to reference a remote NVME subsystem port.
302 * @port_num: NVME-FC transport remote subsystem port number
303 * @port_role: NVME roles are supported on the port (see FC_PORT_ROLE_xxx)
306 * @localport: pointer to the NVME-FC local host port the subsystem is
340 * operational parameters for an LLDD that supports NVME host
342 * NVME-FC transport remembers template reference and may
383 * @ls_req: Called to issue a FC-NVME FC-4 LS service request.
391 * @fcp_io: called to issue a FC-NVME I/O request. The I/O may be for
393 * fully describe the io: the buffer containing the FC-NVME CMD IU
395 * and the buffer to place the FC-NVME RSP IU into. The LLDD will
414 * @xmt_ls_rsp: Called to transmit the response to a FC-NVME FC-4 LS service.
447 * memory that it would like fc nvme layer to allocate on the LLDD's
454 * memory that it would like fc nvme layer to allocate on the LLDD's
461 * memory that it would like fc nvme layer to allocate on the LLDD's
468 * memory that it would like fc nvme layer to allocate on the LLDD's
537 * Routine called to pass a NVME-FC LS request, received by the lldd,
538 * to the nvme-fc transport.
566 * *************** LLDD FC-NVME Target/Subsystem API ***************
568 * For FC LLDD's that are the NVME Subsystem role
575 * data element used during NVME Subsystem role
593 /* Operations that NVME-FC layer may request the LLDD to perform for FCP */
606 * the specific FC-NVME IU operation(s) to perform
607 * for a FC-NVME FCP IO.
610 * context for a FC-NVME FCP I/O operation (e.g. a nvme sqe, the sqe-related
619 * the FCP I/O was received on, the remote FC NVME initiator that sent the
645 * @timeout: amount of time, in seconds, to wait for a response from the NVME
714 * struct nvmet_fc_target_port - structure used between NVME-FC transport and
715 * a LLDD to reference a local NVME subsystem port.
721 * @port_num: NVME-FC transport subsytem port number
753 * and operational parameters for an LLDD that supports NVME
755 * registrations. NVME-FC transport remembers template
766 * @xmt_ls_rsp: Called to transmit the response to a FC-NVME FC-4 LS service.
790 * more FC sequences (preferrably 1). Note: the fc-nvme layer
797 * Note: the FC-NVME layer may call the WRITEDATA operation
811 * may retramsit the FCP_RSP iu if necessary per FC-NVME. Upon
820 * FCP_RSP iu if FCP_CONF is not received per FC-NVME. Upon
835 * operations, the fc-nvme layer may immediate convert, in the same
864 * begun processing of a previously received NVME CMD IU. The LLDD
870 * change notifications to NVME initiators. The RSCN notifications
874 * @ls_req: Called to issue a FC-NVME FC-4 LS service request.
880 * transport is only allowed to issue FC-NVME LS's on behalf of an
930 * memory that it would like fc nvme layer to allocate on the LLDD's
984 * Routine called to pass a NVME-FC LS request, received by the lldd,
1013 * connectivity to a NVME-FC host port which there had been active
1014 * NVMe controllers for. The host port is indicated by the
1016 * when a NVME LS was received, typically to create a new association.