Lines Matching full:structure

23  * struct nvmefc_ls_req - Request structure passed from the transport
42  * @private:  pointer to memory allocated alongside the ls request structure
49  *            request structure. Status argument must be 0 upon success, a
69  * struct nvmefc_ls_rsp - Structure passed from the transport to the LLDD
71  *            NVME-FC LS request.   The structure originates in the LLDD
73  *            transport routine. As such, the structure represents the
83  * The structure is allocated by the LLDD whenever a LS Request is received
84  * from the FC link. The address of the structure is passed to the nvmet-fc
87  * The address of the structure is to be passed back to the LLDD
89  * map back to the LLDD exchange structure which maintains information such
92  * address of the structure back to the transport LS rsp done() routine,
94  * the done() routine, no further access to the structure will be made by
95  * the transport and the LLDD can de-allocate the structure.
99  *     is valid in the structure.
101  *   When the structure is used for the LLDD->xmt_ls_rsp() call, the
115  * @nvme_fc_private:  pointer to an internal transport-specific structure
171  * struct nvmefc_fcp_req - Request structure passed from NVME-FC transport
183  * @sg_table:  scatter/gather structure for payload data
192  *             request structure that is specifically for the LLDD to use
252  * struct nvme_fc_local_port - structure used between NVME-FC transport and
264  *             structure that is specifically for the LLDD to use.
295  * struct nvme_fc_remote_port - structure used between NVME-FC transport and
309  *             structure that is specifically for the LLDD to use.
339  * struct nvme_fc_port_template - structure containing static entrypoints and
384  *       The nvme_fc_ls_req structure will fully describe the buffers for
388  *       structure (argument to done is the ls request structure itself).
392  *       an admin queue or an i/o queue.  The nvmefc_fcp_req structure will
398  *       request structure (argument to done is the fcp request structure
415  *       The nvmefc_ls_rsp structure is the same LLDD-supplied exchange
416  *       structure specified in the nvme_fc_rcv_ls_req() call made when
417  *       the LS request was received. The structure will fully describe
421  *       the "done" routine specified in the nvmefc_ls_rsp structure
422  *       (argument to done is the address of the nvmefc_ls_rsp structure
424  *       consider the LS handling complete and the nvmefc_ls_rsp structure
462  *       behalf whenever a ls request structure is allocated. The additional
469  *       behalf whenever a fcp request structure is allocated. The additional
554  * the lsrsp structure, the transport will still call xmt_ls_rsp()
555  * afterward to cleanup the outstanding lsrsp structure. The LLDD should
557  * to allow the lsrsp structure to be released.
604  * struct nvmefc_tgt_fcp_req - Structure used between LLDD and NVMET-FC
609  * Structure used between LLDD and nvmet-fc layer to represent the exchange
613  * The structure is allocated by the LLDD whenever a FCP CMD IU is received
614  * from the FC link. The address of the structure is passed to the nvmet-fc
615  * layer via the nvmet_fc_rcv_fcp_req() call. The address of the structure
618  * exchange structure which maintains information such as the targetport
621  * operation, the address of the structure will be passed back to the FCP
625  * de-allocate the structure.
629  *     is valid in the structure.
631  *   When the structure is used for an FCP target operation, the nvmet-fc
668  * @nvmet_fc_private:  pointer to an internal NVMET-FC layer structure used
714  * struct nvmet_fc_target_port - structure used between NVME-FC transport and
725  *             structure that is specifically for the LLDD to use.
752  * struct nvmet_fc_target_template - structure containing static entrypoints
767  *       The nvmefc_ls_rsp structure is the same LLDD-supplied exchange
768  *       structure specified in the nvmet_fc_rcv_ls_req() call made when
769  *       the LS request was received. The structure will fully describe
773  *       the "done" routine specified in the nvmefc_ls_rsp structure
774  *       (argument to done is the address of the nvmefc_ls_rsp structure
776  *       consider the LS handling complete and the nvmefc_ls_rsp structure
783  *       The nvmefc_tgt_fcp_req structure is the same LLDD-supplied
784  *       exchange structure specified in the nvmet_fc_rcv_fcp_req() call
786  *       structure shall indicate the operation for the LLDD to perform
830  *       the LLDD-supplied exchange structure must remain valid until the
832  *       of the exchange structure back to the LLDD so that it may be used
875  *       The nvme_fc_ls_req structure will fully describe the buffers for
883  *       nvmefc_ls_rsp structure for the Create Association LS that
891  *       request structure (argument to done is the ls request structure
938  *       behalf whenever a ls request structure is allocated. The additional
1001  * the lsrsp structure, the transport will still call xmt_ls_rsp()
1002  * afterward to cleanup the outstanding lsrsp structure. The LLDD should
1004  * to allow the lsrsp structure to be released.