Lines Matching full:ls
13 * ********************** FC-NVME LS API ********************
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
30 * LS's such as Disconnect Association.
39 * @timeout: Maximum amount of time, in seconds, to wait for the LS response.
40 * If timeout exceeded, LLDD to abort LS exchange and complete
41 * LS request with error status.
42 * @private: pointer to memory allocated alongside the ls request structure
48 * the LS request. req argument is the pointer to the original LS
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
77 * received LS's such as Create Association, Create Connection
80 * received LS's such as Disconnect Association or Disconnect
83 * The structure is allocated by the LLDD whenever a LS Request is received
90 * the remote N_Port that sent the LS as well as any FC exchange context.
91 * Upon completion of the LS response transmit, the LLDD will pass the
92 * address of the structure back to the transport LS rsp done() routine,
109 * @rspbuf: pointer to the LS response buffer
110 * @rspdma: PCI DMA address of the LS response buffer
111 * @rsplen: Length, in bytes, of the LS response buffer
113 * transmitting the LS response. req argument is the pointer to
114 * the original ls request.
383 * @ls_req: Called to issue a FC-NVME FC-4 LS service request.
386 * LLDD is to allocate an exchange, issue the LS request, obtain the
387 * LS response, and call the "done" routine specified in the request
388 * structure (argument to done is the ls request structure itself).
402 * @ls_abort: called to request the LLDD to abort the indicated ls request.
404 * the request, the LLDD must still call the ls request done routine
414 * @xmt_ls_rsp: Called to transmit the response to a FC-NVME FC-4 LS service.
417 * the LS request was received. The structure will fully describe
424 * consider the LS handling complete and the nvmefc_ls_rsp structure
462 * behalf whenever a ls request structure is allocated. The additional
537 * Routine called to pass a NVME-FC LS request, received by the lldd,
540 * If the return value is zero: the LS was successfully accepted by the
543 * LS. The lldd should ABTS-LS the LS.
545 * Note: if the LLDD receives and ABTS for the LS prior to the transport
547 * shall mark the LS as aborted, and when the xmt_ls_rsp() is called: the
550 * soon as the LS was marked or can delay until the xmt_ls_rsp() call is
552 * Note: if an RCV LS was successfully posted to the transport and the
766 * @xmt_ls_rsp: Called to transmit the response to a FC-NVME FC-4 LS service.
769 * the LS request was received. The structure will fully describe
776 * consider the LS handling complete and the nvmefc_ls_rsp structure
779 * LS received.
874 * @ls_req: Called to issue a FC-NVME FC-4 LS service request.
877 * The targetport that is to issue the LS request is identified by
879 * LS request is identified by the hosthandle argument. The nvmet-fc
880 * transport is only allowed to issue FC-NVME LS's on behalf of an
881 * association that was created prior by a Create Association LS.
883 * nvmefc_ls_rsp structure for the Create Association LS that
889 * The LLDD is to allocate an exchange, issue the LS request, obtain
890 * the LS response, and call the "done" routine specified in the
891 * request structure (argument to done is the ls request structure
895 * @ls_abort: called to request the LLDD to abort the indicated ls request.
897 * the request, the LLDD must still call the ls request done routine
938 * behalf whenever a ls request structure is allocated. The additional
984 * Routine called to pass a NVME-FC LS request, received by the lldd,
987 * If the return value is zero: the LS was successfully accepted by the
990 * LS. The lldd should ABTS-LS the LS.
992 * Note: if the LLDD receives and ABTS for the LS prior to the transport
994 * shall mark the LS as aborted, and when the xmt_ls_rsp() is called: the
997 * soon as the LS was marked or can delay until the xmt_ls_rsp() call is
999 * Note: if an RCV LS was successfully posted to the transport and the
1016 * when a NVME LS was received, typically to create a new association.
1018 * association for use in LS requests for the association.
1024 * part of sending LS's to terminate the association. The LLDD
1025 * should reject the LS's if they are attempted.
1036 * the FCP cmd. The lldd should ABTS-LS the cmd.