Lines Matching full:the
24 * struct nvmefc_ls_req - Request structure passed from the transport
25 * to the LLDD to perform a NVME-FC LS request and obtain
30 * Used by the nvmet-fc transport (controller) to send
33 * Values set by the requestor prior to calling the LLDD ls_req entrypoint:
40 * @timeout: Maximum amount of time, in seconds, to wait for the LS response.
43 * @private: pointer to memory allocated alongside the ls request structure
44 * that is specifically for the LLDD to use while processing the
45 * request. The length of the buffer corresponds to the
46 * lsrqst_priv_sz value specified in the xxx_template supplied
47 * by the LLDD.
48 * @done: The callback routine the LLDD is to invoke upon completion of
49 * the LS request. req argument is the pointer to the original LS
70 * struct nvmefc_ls_rsp - Structure passed from the transport to the LLDD
71 * to request the transmit the NVME-FC LS response to a
72 * NVME-FC LS request. The structure originates in the LLDD
73 * and is given to the transport via the xxx_rcv_ls_req()
74 * transport routine. As such, the structure represents the
75 * FC exchange context for the NVME-FC LS request that was
76 * received and which the response is to be sent for.
77 * Used by the LLDD to pass the nvmet-fc transport (controller)
80 * Used by the LLDD to pass the nvme-fc transport (host)
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
86 * or nvme-fc layer via the xxx_rcv_ls_req() transport routines.
88 * The address of the structure is to be passed back to the LLDD
89 * when the response is to be transmit. The LLDD will use the address to
90 * map back to the LLDD exchange structure which maintains information such
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,
94 * allowing the transport release dma resources. Upon completion of
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.
99 * At the time of the xxx_rcv_ls_req() call, there is no content that
100 * is valid in the structure.
102 * When the structure is used for the LLDD->xmt_ls_rsp() call, the
103 * transport layer will fully set the fields in order to specify the
104 * response payload buffer and its length as well as the done routine
105 * to be called upon completion of the transmit. The transport layer
106 * will also set a private pointer for its own use in the done routine.
108 * Values set by the transport layer prior to calling the LLDD xmt_ls_rsp
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
113 * @done: The callback routine the LLDD is to invoke upon completion of
114 * transmitting the LS response. req argument is the pointer to
115 * the original ls request.
117 * used as part of the transport done() processing. The LLDD is
134 * For FC LLDD's that are the NVME Host role.
145 * Static fields describing the port being registered:
146 * @node_name: FC WWNN for the port
147 * @port_name: FC WWPN for the port
153 * @port_id: FC N_Port_ID currently assigned the port. Upper 8 bits must
175 * Values set by the NVME-FC layer prior to calling the LLDD fcp_io
177 * @cmdaddr: pointer to the FCP CMD IU buffer
178 * @rspaddr: pointer to the FCP RSP IU buffer
179 * @cmddma: PCI DMA address of the FCP CMD IU buffer
180 * @rspdma: PCI DMA address of the FCP RSP IU buffer
181 * @cmdlen: Length, in bytes, of the FCP CMD IU buffer
182 * @rsplen: Length, in bytes, of the FCP RSP IU buffer
186 * @sg_cnt: number of elements in the scatter/gather list
187 * @io_dir: direction of the FCP request (see NVMEFC_FCP_xxx)
188 * @done: The callback routine the LLDD is to invoke upon completion of
189 * the FCP operation. req argument is the pointer to the original
191 * @private: pointer to memory allocated alongside the FCP operation
192 * request structure that is specifically for the LLDD to use
193 * while processing the operation. The length of the buffer
194 * corresponds to the fcprqst_priv_sz value specified in the
195 * nvme_fc_port_template supplied by the LLDD.
196 * @sqid: The nvme SQID the command is being issued on
198 * Values set by the LLDD indicating completion status of the FCP operation.
199 * Must be set prior to calling the done() callback.
200 * @rcv_rsplen: length, in bytes, of the FCP RSP IU received.
203 * @status: Completion status of the FCP operation. must be 0 upon success,
205 * NOT a reflection of the NVME CQE completion status. Only the
206 * status of the FCP operation at the NVME-FC level.
255 * Allocated/created by the nvme_fc_register_localport()
258 * Fields with static values for the port. Initialized by the
259 * port_info struct supplied to the registration call.
261 * @port_role: NVME roles are supported on the port (see FC_PORT_ROLE_xxx)
262 * @node_name: FC WWNN for the port
263 * @port_name: FC WWPN for the port
264 * @private: pointer to memory allocated alongside the local port
265 * structure that is specifically for the LLDD to use.
266 * The length of the buffer corresponds to the local_priv_sz
267 * value specified in the nvme_fc_port_template supplied by
268 * the LLDD.
274 * may reference fields directly to change them. Initialized by the
275 * port_info struct supplied to the registration call.
276 * @port_id: FC N_Port_ID currently assigned the port. Upper 8 bits must
278 * @port_state: Operational state of the port.
298 * Allocated/created by the nvme_fc_register_remoteport()
301 * Fields with static values for the port. Initialized by the
302 * port_info struct supplied to the registration call.
304 * @port_role: NVME roles are supported on the port (see FC_PORT_ROLE_xxx)
305 * @node_name: FC WWNN for the port
306 * @port_name: FC WWPN for the port
307 * @localport: pointer to the NVME-FC local host port the subsystem is
309 * @private: pointer to memory allocated alongside the remote port
310 * structure that is specifically for the LLDD to use.
311 * The length of the buffer corresponds to the remote_priv_sz
312 * value specified in the nvme_fc_port_template supplied by
313 * the LLDD.
317 * the port_info struct supplied to the registration call.
318 * @port_id: FC N_Port_ID currently assigned the port. Upper 8 bits must
320 * @port_state: Operational state of the remote port. Valid values are
348 * @localport_delete: The LLDD initiates deletion of a localport via
349 * nvme_fc_deregister_localport(). However, the teardown is
350 * asynchronous. This routine is called upon the completion of the
351 * teardown to inform the LLDD that the localport has been deleted.
354 * @remoteport_delete: The LLDD initiates deletion of a remoteport via
355 * nvme_fc_deregister_remoteport(). However, the teardown is
356 * asynchronous. This routine is called upon the completion of the
357 * teardown to inform the LLDD that the remoteport has been deleted.
362 * callback into the LLDD to notify that a controller queue is being
363 * created. The LLDD may choose to allocate an associated hw queue
364 * or map it onto a shared hw queue. Upon return from the call, the
366 * command that is posted to the controller queue. The handle can
367 * be used by the LLDD to map quickly to the proper hw queue for
368 * command execution. The mask of cpu's that will map to this queue
369 * at the block-level is also passed in. The LLDD should use the
370 * queue id and/or cpu masks to ensure proper affinitization of the
371 * controller queue to the hw queue.
374 * @delete_queue: This is the inverse of the crete_queue. During
377 * a hw queue should be termined. If there is a unique hw queue, the
381 * @poll_queue: Called to poll for the completion of an io on a blk queue.
385 * The nvme_fc_ls_req structure will fully describe the buffers for
386 * the request payload and where to place the response payload. The
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).
392 * @fcp_io: called to issue a FC-NVME I/O request. The I/O may be for
393 * an admin queue or an i/o queue. The nvmefc_fcp_req structure will
394 * fully describe the io: the buffer containing the FC-NVME CMD IU
395 * (which contains the SQE), the sg list for the payload if applicable,
396 * and the buffer to place the FC-NVME RSP IU into. The LLDD will
397 * complete the i/o, indicating the amount of data transferred or
398 * any transport error, and call the "done" routine specified in the
399 * request structure (argument to done is the fcp request structure
403 * @ls_abort: called to request the LLDD to abort the indicated ls request.
404 * The call may return before the abort has completed. After aborting
405 * the request, the LLDD must still call the ls request done routine
409 * @fcp_abort: called to request the LLDD to abort the indicated fcp request.
410 * The call may return before the abort has completed. After aborting
411 * the request, the LLDD must still call the fcp request done routine
415 * @xmt_ls_rsp: Called to transmit the response to a FC-NVME FC-4 LS service.
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
419 * the buffers for the response payload and the dma address of the
420 * payload. The LLDD is to transmit the response (or return a
421 * non-zero errno status), and upon completion of the transmit, call
422 * the "done" routine specified in the nvmefc_ls_rsp structure
423 * (argument to done is the address of the nvmefc_ls_rsp structure
424 * itself). Upon the completion of the done routine, the LLDD shall
425 * consider the LS handling complete and the nvmefc_ls_rsp structure
427 * Entrypoint is mandatory if the LLDD calls the nvme_fc_rcv_ls_req()
430 * @max_hw_queues: indicates the maximum number of hw queues the LLDD
434 * @max_sgl_segments: indicates the maximum number of sgl segments supported
435 * by the LLDD
438 * @max_dif_sgl_segments: indicates the maximum number of sgl segments
439 * supported by the LLDD for DIF operations.
442 * @dma_boundary: indicates the dma address boundary where dma mappings
447 * @local_priv_sz: The LLDD sets this field to the amount of additional
448 * memory that it would like fc nvme layer to allocate on the LLDD's
449 * behalf whenever a localport is allocated. The additional memory
450 * area solely for the of the LLDD and its location is specified by
451 * the localport->private pointer.
454 * @remote_priv_sz: The LLDD sets this field to the amount of additional
455 * memory that it would like fc nvme layer to allocate on the LLDD's
456 * behalf whenever a remoteport is allocated. The additional memory
457 * area solely for the of the LLDD and its location is specified by
458 * the remoteport->private pointer.
461 * @lsrqst_priv_sz: The LLDD sets this field to the amount of additional
462 * memory that it would like fc nvme layer to allocate on the LLDD's
463 * behalf whenever a ls request structure is allocated. The additional
464 * memory area is solely for use by the LLDD and its location is
465 * specified by the ls_request->private pointer.
468 * @fcprqst_priv_sz: The LLDD sets this field to the amount of additional
469 * memory that it would like fc nvme layer to allocate on the LLDD's
470 * behalf whenever a fcp request structure is allocated. The additional
471 * memory area solely for the of the LLDD and its location is
472 * specified by the fcp_request->private pointer.
540 * Routine called to pass a NVME-FC LS request, received by the lldd,
541 * to the nvme-fc transport.
543 * If the return value is zero: the LS was successfully accepted by the
545 * If the return value is non-zero: the transport has not accepted 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
549 * calling the ops->xmt_ls_rsp() routine to transmit a response, the LLDD
550 * shall mark the LS as aborted, and when the xmt_ls_rsp() is called: the
551 * response shall not be transmit and the struct nvmefc_ls_rsp() done
552 * routine shall be called. The LLDD may transmit the ABTS response as
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
557 * the lsrsp structure, the transport will still call xmt_ls_rsp()
558 * afterward to cleanup the outstanding lsrsp structure. The LLDD should
559 * noop the transmission of the rsp and call the lsrsp->done() routine
560 * to allow the lsrsp structure to be released.
568 * Routine called to get the appid field associated with request by the lldd
570 * If the return value is NULL : the user/libvirt has not set the appid to VM
571 * If the return value is non-zero: Returns the appid associated with VM
580 * For FC LLDD's that are the NVME Subsystem role
590 * Static fields describing the port being registered:
591 * @node_name: FC WWNN for the port
592 * @port_name: FC WWPN for the port
595 * @port_id: FC N_Port_ID currently assigned the port. Upper 8 bits must
605 /* Operations that NVME-FC layer may request the LLDD to perform for FCP */
617 * layer to represent the exchange context and
618 * the specific FC-NVME IU operation(s) to perform
621 * Structure used between LLDD and nvmet-fc layer to represent the exchange
622 * context for a FC-NVME FCP I/O operation (e.g. a nvme sqe, the sqe-related
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
628 * will be passed back to the LLDD for the data operations and transmit of
629 * the response. The LLDD is to use the address to map back to the LLDD
630 * exchange structure which maintains information such as the targetport
631 * the FCP I/O was received on, the remote FC NVME initiator that sent the
632 * FCP I/O, and any FC exchange context. Upon completion of the FCP target
633 * operation, the address of the structure will be passed back to the FCP
634 * op done() routine, allowing the nvmet-fc layer to release dma resources.
635 * Upon completion of the done() routine for either RSP or ABORT ops, no
636 * further access will be made by the nvmet-fc layer and the LLDD can
637 * de-allocate the structure.
640 * At the time of the nvmet_fc_rcv_fcp_req() call, there is no content that
641 * is valid in the structure.
643 * When the structure is used for an FCP target operation, the nvmet-fc
644 * layer will fully set the fields in order to specify the scattergather
645 * list, the transfer length, as well as the done routine to be called
646 * upon compeletion of the operation. The nvmet-fc layer will also set a
647 * private pointer for its own use in the done routine.
649 * Values set by the NVMET-FC layer prior to calling the LLDD fcp_op
651 * @op: Indicates the FCP IU operation to perform (see NVMET_FCOP_xxx)
652 * @hwqid: Specifies the hw queue index (0..N-1, where N is the
653 * max_hw_queues value from the LLD's nvmet_fc_target_template)
654 * that the operation is to use.
655 * @offset: Indicates the DATA_OUT/DATA_IN payload offset to be tranferred.
657 * @timeout: amount of time, in seconds, to wait for a response from the NVME
659 * Valid only for the following ops:
660 * WRITEDATA: caps the wait for data reception
662 * @transfer_length: the length, in bytes, of the DATA_OUT or DATA_IN payload
664 * Valid only for the WRITEDATA, READDATA, or READDATA_RSP ops.
665 * @ba_rjt: Contains the BA_RJT payload that is to be transferred.
666 * Valid only for the NVMET_FCOP_BA_RJT op.
667 * @sg: Scatter/gather list for the DATA_OUT/DATA_IN payload data.
668 * Valid only for the WRITEDATA, READDATA, or READDATA_RSP ops.
669 * @sg_cnt: Number of valid entries in the scatter/gather list.
670 * Valid only for the WRITEDATA, READDATA, or READDATA_RSP ops.
671 * @rspaddr: pointer to the FCP RSP IU buffer to be transmit
673 * @rspdma: PCI DMA address of the FCP RSP IU buffer
675 * @rsplen: Length, in bytes, of the FCP RSP IU buffer
677 * @done: The callback routine the LLDD is to invoke upon completion of
678 * the operation. req argument is the pointer to the original
681 * as part of the NVMET-FC processing. The LLDD is not to
684 * Values set by the LLDD indicating completion status of the FCP operation.
685 * Must be set prior to calling the done() callback.
689 * @fcp_error: status of the FCP operation. Must be 0 on success; on failure
717 /* Bit 0: supports the NVMET_FCPOP_READDATA_RSP op, which
718 * sends (the last) Read Data sequence followed by the RSP
728 * Allocated/created by the nvme_fc_register_targetport()
731 * Fields with static values for the port. Initialized by the
732 * port_info struct supplied to the registration call.
734 * @node_name: FC WWNN for the port
735 * @port_name: FC WWPN for the port
736 * @private: pointer to memory allocated alongside the local port
737 * structure that is specifically for the LLDD to use.
738 * The length of the buffer corresponds to the target_priv_sz
739 * value specified in the nvme_fc_target_template supplied by
740 * the LLDD.
743 * may reference fields directly to change them. Initialized by the
744 * port_info struct supplied to the registration call.
745 * @port_id: FC N_Port_ID currently assigned the port. Upper 8 bits must
747 * @port_state: Operational state of the port.
772 * @targetport_delete: The LLDD initiates deletion of a targetport via
773 * nvmet_fc_unregister_targetport(). However, the teardown is
774 * asynchronous. This routine is called upon the completion of the
775 * teardown to inform the LLDD that the targetport has been deleted.
778 * @xmt_ls_rsp: Called to transmit the response to a FC-NVME FC-4 LS service.
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
782 * the buffers for the response payload and the dma address of the
783 * payload. The LLDD is to transmit the response (or return a
784 * non-zero errno status), and upon completion of the transmit, call
785 * the "done" routine specified in the nvmefc_ls_rsp structure
786 * (argument to done is the address of the nvmefc_ls_rsp structure
787 * itself). Upon the completion of the done() routine, the LLDD shall
788 * consider the LS handling complete and the nvmefc_ls_rsp structure
790 * The transport will always call the xmt_ls_rsp() routine for any
794 * @map_queues: This functions lets the driver expose the queue mapping
795 * to the block layer.
799 * The nvmefc_tgt_fcp_req structure is the same LLDD-supplied
800 * exchange structure specified in the nvmet_fc_rcv_fcp_req() call
801 * made when the FCP CMD IU was received. The op field in the
802 * structure shall indicate the operation for the LLDD to perform
803 * relative to the io.
804 * NVMET_FCOP_READDATA operation: the LLDD is to send the
805 * payload data (described by sglist) to the host in 1 or
806 * more FC sequences (preferrably 1). Note: the fc-nvme layer
807 * may call the READDATA operation multiple times for longer
809 * NVMET_FCOP_WRITEDATA operation: the LLDD is to receive the
810 * payload data (described by sglist) from the host via 1 or
811 * more FC sequences (preferrably 1). The LLDD is to generate
812 * the XFER_RDY IU(s) corresponding to the data being requested.
813 * Note: the FC-NVME layer may call the WRITEDATA operation
815 * NVMET_FCOP_READDATA_RSP operation: the LLDD is to send the
816 * payload data (described by sglist) to the host in 1 or
818 * payload data transmission, the LLDD is to set the
820 * consider the operation complete. On error, the LLDD is to not
821 * transmit the FCP_RSP iu. If all payload data is transferred
822 * successfully, the LLDD is to update the nvmefc_tgt_fcp_req
823 * transferred_length field and may subsequently transmit the
825 * If FCP_CONF is supported, the LLDD is to await FCP_CONF
826 * reception to confirm the RSP reception by the host. The LLDD
827 * may retramsit the FCP_RSP iu if necessary per FC-NVME. Upon
828 * transmission of the FCP_RSP iu if FCP_CONF is not supported,
829 * or upon success/failure of FCP_CONF if it is supported, the
830 * LLDD is to set the nvmefc_tgt_fcp_req fcp_error field and
831 * consider the operation complete.
832 * NVMET_FCOP_RSP: the LLDD is to transmit the FCP_RSP iu payload
834 * supported, the LLDD is to await FCP_CONF reception to confirm
835 * the RSP reception by the host. The LLDD may retramsit the
837 * transmission of the FCP_RSP iu if FCP_CONF is not supported,
838 * or upon success/failure of FCP_CONF if it is supported, the
839 * LLDD is to set the nvmefc_tgt_fcp_req fcp_error field and
840 * consider the operation complete.
841 * Upon completing the indicated operation, the LLDD is to set the
842 * status fields for the operation (tranferred_length and fcp_error
843 * status) in the request, then call the "done" routine
844 * indicated in the fcp request. After the operation completes,
845 * regardless of whether the FCP_RSP iu was successfully transmit,
846 * the LLDD-supplied exchange structure must remain valid until the
847 * transport calls the fcp_req_release() callback to return ownership
848 * of the exchange structure back to the LLDD so that it may be used
850 * Note: when calling the done routine for READDATA or WRITEDATA
851 * operations, the fc-nvme layer may immediate convert, in the same
852 * thread and before returning to the LLDD, the fcp operation to
853 * the next operation for the fcp io and call the LLDDs fcp_op
854 * call again. If fields in the fcp request are to be accessed post
855 * the done call, the LLDD should save their values prior to calling
856 * the done routine, and inspect the save values after the done
861 * @fcp_abort: Called by the transport to abort an active command.
862 * The command may be in-between operations (nothing active in LLDD)
863 * or may have an active WRITEDATA operation pending. The LLDD is to
864 * initiate the ABTS process for the command and return from the
865 * callback. The ABTS does not need to be complete on the command.
866 * The fcp_abort callback inherently cannot fail. After the
867 * fcp_abort() callback completes, the transport will wait for any
869 * call the fcp_req_release() callback to return the command's
870 * exchange context back to the LLDD.
873 * @fcp_req_release: Called by the transport to return a nvmefc_tgt_fcp_req
874 * to the LLDD after all operations on the fcp operation are complete.
875 * This may be due to the command completing or upon completion of
879 * @defer_rcv: Called by the transport to signal the LLLD that it has
880 * begun processing of a previously received NVME CMD IU. The LLDD
881 * is now free to re-use the rcv buffer associated with the
885 * @discovery_event: Called by the transport to generate an RSCN
886 * change notifications to NVME initiators. The RSCN notifications
887 * should cause the initiator to rescan the discovery controller
888 * on the targetport.
891 * The nvme_fc_ls_req structure will fully describe the buffers for
892 * the request payload and where to place the response payload.
893 * The targetport that is to issue the LS request is identified by
894 * the targetport argument. The remote port that is to receive the
895 * LS request is identified by the hosthandle argument. The nvmet-fc
898 * The hosthandle will originate from the LLDD in the struct
899 * nvmefc_ls_rsp structure for the Create Association LS that
900 * was delivered to the transport. The transport will save the
901 * hosthandle as an attribute of the association. If the LLDD
902 * loses connectivity with the remote port, it must call the
904 * the remote port in the transport.
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.
912 * The call may return before the abort has completed. After aborting
913 * the request, the LLDD must still call the ls request done routine
915 * Entrypoint is Mandatory if the ls_req entry point is specified.
917 * @host_release: called to inform the LLDD that the request to invalidate
918 * the host port indicated by the hosthandle has been fully completed.
919 * No associations exist with the host port and there will be no
921 * Entrypoint is Mandatory if the lldd calls nvmet_fc_invalidate_host().
923 * @host_traddr: called by the transport to retrieve the node name and
924 * port name of the host port address.
926 * @max_hw_queues: indicates the maximum number of hw queues the LLDD
930 * @max_sgl_segments: indicates the maximum number of sgl segments supported
931 * by the LLDD
934 * @max_dif_sgl_segments: indicates the maximum number of sgl segments
935 * supported by the LLDD for DIF operations.
938 * @dma_boundary: indicates the dma address boundary where dma mappings
943 * @target_features: The LLDD sets bits in this field to correspond to
944 * optional features that are supported by the LLDD.
945 * Refer to the NVMET_FCTGTFEAT_xxx values.
948 * @target_priv_sz: The LLDD sets this field to the amount of additional
949 * memory that it would like fc nvme layer to allocate on the LLDD's
950 * behalf whenever a targetport is allocated. The additional memory
951 * area solely for the of the LLDD and its location is specified by
952 * the targetport->private pointer.
955 * @lsrqst_priv_sz: The LLDD sets this field to the amount of additional
956 * memory that it would like nvmet-fc layer to allocate on the LLDD's
957 * behalf whenever a ls request structure is allocated. The additional
958 * memory area is solely for use by the LLDD and its location is
959 * specified by the ls_request->private pointer.
1004 * Routine called to pass a NVME-FC LS request, received by the lldd,
1005 * to the nvmet-fc transport.
1007 * If the return value is zero: the LS was successfully accepted by the
1009 * If the return value is non-zero: the transport has not accepted 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
1013 * calling the ops->xmt_ls_rsp() routine to transmit a response, the LLDD
1014 * shall mark the LS as aborted, and when the xmt_ls_rsp() is called: the
1015 * response shall not be transmit and the struct nvmefc_ls_rsp() done
1016 * routine shall be called. The LLDD may transmit the ABTS response as
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
1021 * the lsrsp structure, the transport will still call xmt_ls_rsp()
1022 * afterward to cleanup the outstanding lsrsp structure. The LLDD should
1023 * noop the transmission of the rsp and call the lsrsp->done() routine
1024 * to allow the lsrsp structure to be released.
1032 * Routine called by the LLDD whenever it has a logout or loss of
1034 * NVMe controllers for. The host port is indicated by the
1035 * hosthandle. The hosthandle is given to the nvmet-fc transport
1037 * The nvmet-fc transport will cache the hostport value with the
1038 * association for use in LS requests for the association.
1039 * When the LLDD calls this routine, the nvmet-fc transport will
1041 * the hosthandle host port.
1042 * The LLDD, after calling this routine and having control returned,
1043 * must assume the transport may subsequently utilize hosthandle as
1044 * part of sending LS's to terminate the association. The LLDD
1045 * should reject the LS's if they are attempted.
1046 * Once the last association has terminated for the hosthandle host
1047 * port, the nvmet-fc transport will call the ops->host_release()
1048 * callback. As of the callback, the nvmet-fc transport will no
1055 * If nvmet_fc_rcv_fcp_req returns non-zero, the transport has not accepted
1056 * the FCP cmd. The lldd should ABTS-LS the cmd.
1065 * add a define, visible to the compiler, that indicates support