Lines Matching full:structure

24  * struct nvmefc_ls_req - Request structure passed from the transport
43  * @private:  pointer to memory allocated alongside the ls request structure
50  *            request structure. Status argument must be 0 upon success, a
70  * struct nvmefc_ls_rsp - Structure passed from the transport to the LLDD
72  *            NVME-FC LS request.   The structure originates in the LLDD
74  *            transport routine. As such, the structure represents the
84  * The structure is allocated by the LLDD whenever a LS Request is received
85  * from the FC link. The address of the structure is passed to the nvmet-fc
88  * The address of the structure is to be passed back to the LLDD
90  * map back to the LLDD exchange structure which maintains information such
93  * address of the structure back to the transport LS rsp done() routine,
95  * the done() routine, no further access to the structure will be made by
96  * the transport and the LLDD can de-allocate the structure.
100  *     is valid in the structure.
102  *   When the structure is used for the LLDD->xmt_ls_rsp() call, the
116  * @nvme_fc_private:  pointer to an internal transport-specific structure
172  * struct nvmefc_fcp_req - Request structure passed from NVME-FC transport
184  * @sg_table:  scatter/gather structure for payload data
193  *             request structure that is specifically for the LLDD to use
253  * struct nvme_fc_local_port - structure used between NVME-FC transport and
265  *             structure that is specifically for the LLDD to use.
296  * struct nvme_fc_remote_port - structure used between NVME-FC transport and
310  *             structure that is specifically for the LLDD to use.
340  * struct nvme_fc_port_template - structure containing static entrypoints and
385  *       The nvme_fc_ls_req structure will fully describe the buffers for
389  *       structure (argument to done is the ls request structure itself).
393  *       an admin queue or an i/o queue.  The nvmefc_fcp_req structure will
399  *       request structure (argument to done is the fcp request structure
416  *       The nvmefc_ls_rsp structure is the same LLDD-supplied exchange
417  *       structure specified in the nvme_fc_rcv_ls_req() call made when
418  *       the LS request was received. The structure will fully describe
422  *       the "done" routine specified in the nvmefc_ls_rsp structure
423  *       (argument to done is the address of the nvmefc_ls_rsp structure
425  *       consider the LS handling complete and the nvmefc_ls_rsp structure
463  *       behalf whenever a ls request structure is allocated. The additional
470  *       behalf whenever a fcp request structure is allocated. The additional
557  * the lsrsp structure, the transport will still call xmt_ls_rsp()
558  * afterward to cleanup the outstanding lsrsp structure. The LLDD should
560  * to allow the lsrsp structure to be released.
616  * struct nvmefc_tgt_fcp_req - Structure used between LLDD and NVMET-FC
621  * Structure used between LLDD and nvmet-fc layer to represent the exchange
625  * The structure is allocated by the LLDD whenever a FCP CMD IU is received
626  * from the FC link. The address of the structure is passed to the nvmet-fc
627  * layer via the nvmet_fc_rcv_fcp_req() call. The address of the structure
630  * exchange structure which maintains information such as the targetport
633  * operation, the address of the structure will be passed back to the FCP
637  * de-allocate the structure.
641  *     is valid in the structure.
643  *   When the structure is used for an FCP target operation, the nvmet-fc
680  * @nvmet_fc_private:  pointer to an internal NVMET-FC layer structure used
726  * struct nvmet_fc_target_port - structure used between NVME-FC transport and
737  *             structure that is specifically for the LLDD to use.
764  * struct nvmet_fc_target_template - structure containing static entrypoints
779  *       The nvmefc_ls_rsp structure is the same LLDD-supplied exchange
780  *       structure specified in the nvmet_fc_rcv_ls_req() call made when
781  *       the LS request was received. The structure will fully describe
785  *       the "done" routine specified in the nvmefc_ls_rsp structure
786  *       (argument to done is the address of the nvmefc_ls_rsp structure
788  *       consider the LS handling complete and the nvmefc_ls_rsp structure
799  *       The nvmefc_tgt_fcp_req structure is the same LLDD-supplied
800  *       exchange structure specified in the nvmet_fc_rcv_fcp_req() call
802  *       structure shall indicate the operation for the LLDD to perform
846  *       the LLDD-supplied exchange structure must remain valid until the
848  *       of the exchange structure back to the LLDD so that it may be used
891  *       The nvme_fc_ls_req structure will fully describe the buffers for
899  *       nvmefc_ls_rsp structure for the Create Association LS that
907  *       request structure (argument to done is the ls request structure
954  *       behalf whenever a ls request structure is allocated. The additional
1017  * the lsrsp structure, the transport will still call xmt_ls_rsp()
1018  * afterward to cleanup the outstanding lsrsp structure. The LLDD should
1020  * to allow the lsrsp structure to be released.