Lines Matching full:ls
14 * ********************** FC-NVME LS API ********************
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
31 * LS's such as Disconnect Association.
40 * @timeout: Maximum amount of time, in seconds, to wait for the LS response.
41 * If timeout exceeded, LLDD to abort LS exchange and complete
42 * LS request with error status.
43 * @private: pointer to memory allocated alongside the ls request structure
49 * the LS request. req argument is the pointer to the original LS
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
78 * received LS's such as Create Association, Create Connection
81 * received LS's such as Disconnect Association or Disconnect
84 * The structure is allocated by the LLDD whenever a LS Request is received
91 * the remote N_Port that sent the LS as well as any FC exchange context.
92 * Upon completion of the LS response transmit, the LLDD will pass the
93 * address of the structure back to the transport LS rsp done() routine,
110 * @rspbuf: pointer to the LS response buffer
111 * @rspdma: PCI DMA address of the LS response buffer
112 * @rsplen: Length, in bytes, of the LS response buffer
114 * transmitting the LS response. req argument is the pointer to
115 * the original ls request.
384 * @ls_req: Called to issue a FC-NVME FC-4 LS service request.
387 * LLDD is to allocate an exchange, issue the LS request, obtain the
388 * LS response, and call the "done" routine specified in the request
389 * structure (argument to done is the ls request structure itself).
403 * @ls_abort: called to request the LLDD to abort the indicated ls request.
405 * the request, the LLDD must still call the ls request done routine
415 * @xmt_ls_rsp: Called to transmit the response to a FC-NVME FC-4 LS service.
418 * the LS request was received. The structure will fully describe
425 * consider the LS handling complete and the nvmefc_ls_rsp structure
463 * behalf whenever a ls request structure is allocated. The additional
540 * Routine called to pass a NVME-FC LS request, received by the lldd,
543 * If the return value is zero: the LS was successfully accepted by the
546 * LS. The lldd should ABTS-LS the LS.
548 * Note: if the LLDD receives and ABTS for the LS prior to the transport
550 * shall mark the LS as aborted, and when the xmt_ls_rsp() is called: the
553 * soon as the LS was marked or can delay until the xmt_ls_rsp() call is
555 * Note: if an RCV LS was successfully posted to the transport and the
778 * @xmt_ls_rsp: Called to transmit the response to a FC-NVME FC-4 LS service.
781 * the LS request was received. The structure will fully describe
788 * consider the LS handling complete and the nvmefc_ls_rsp structure
791 * LS received.
890 * @ls_req: Called to issue a FC-NVME FC-4 LS service request.
893 * The targetport that is to issue the LS request is identified by
895 * LS request is identified by the hosthandle argument. The nvmet-fc
896 * transport is only allowed to issue FC-NVME LS's on behalf of an
897 * association that was created prior by a Create Association LS.
899 * nvmefc_ls_rsp structure for the Create Association LS that
905 * The LLDD is to allocate an exchange, issue the LS request, obtain
906 * the LS response, and call the "done" routine specified in the
907 * request structure (argument to done is the ls request structure
911 * @ls_abort: called to request the LLDD to abort the indicated ls request.
913 * the request, the LLDD must still call the ls request done routine
957 * behalf whenever a ls request structure is allocated. The additional
1004 * Routine called to pass a NVME-FC LS request, received by the lldd,
1007 * If the return value is zero: the LS was successfully accepted by the
1010 * LS. The lldd should ABTS-LS the LS.
1012 * Note: if the LLDD receives and ABTS for the LS prior to the transport
1014 * shall mark the LS as aborted, and when the xmt_ls_rsp() is called: the
1017 * soon as the LS was marked or can delay until the xmt_ls_rsp() call is
1019 * Note: if an RCV LS was successfully posted to the transport and the
1036 * when a NVME LS was received, typically to create a new association.
1038 * association for use in LS requests for the association.
1044 * part of sending LS's to terminate the association. The LLDD
1045 * should reject the LS's if they are attempted.
1056 * the FCP cmd. The lldd should ABTS-LS the cmd.