Lines Matching full:nvme
13 #include "nvme.h"
15 #include <linux/nvme-fc-driver.h>
16 #include <linux/nvme-fc.h>
91 * nvme/host/core.c
237 /* *********************** FC-NVME Port Management ************************ */
339 * LLDD to register the existence of a NVME
455 * registered a NVME host FC port.
491 * TRADDR strings, per FC-NVME are fixed format:
568 "NVME-FC{%d}: connectivity re-established. " in nvme_fc_resume_controller()
657 * LLDD to register the existence of a NVME
793 "NVME-FC{%d}: controller connectivity lost. Awaiting " in nvme_fc_ctrl_connectivity_loss()
808 "NVME-FC{%d}: Couldn't schedule reset.\n", in nvme_fc_ctrl_connectivity_loss()
844 * registered a NVME subsystem FC port.
876 "NVME-FC{%d}: controller connectivity lost.\n", in nvme_fc_unregister_remoteport()
903 * LLDD to request a nvme device rescan.
942 /* *********************** FC-NVME DMA Handling **************************** */
1030 /* *********************** FC-NVME LS Handling **************************** */
1192 "NVME-FC{%d}: send Create Association failed: ENOMEM\n", in nvme_fc_connect_admin_queue()
1308 "NVME-FC{%d}: send Create Connection failed: ENOMEM\n", in nvme_fc_connect_queue()
1402 /* fc-nvme initiator doesn't care about success or failure of cmd */ in nvme_fc_disconnect_assoc_done()
1408 * This routine sends a FC-NVME LS to disconnect (aka terminate)
1409 * the FC-NVME Association. Terminating the association also
1410 * terminates the FC-NVME connections (per queue, both admin and io
1412 * down, and the related FC-NVME Association ID and Connection IDs
1415 * The behavior of the fc-nvme initiator is such that it's
1418 * connectivity with the fc-nvme target, so you may never get a
1421 * continue on with terminating the association. If the fc-nvme target
1438 "NVME-FC{%d}: send Disconnect Association " in nvme_fc_xmt_disconnect_assoc()
1539 "NVME-FC{%d}: Multiple Disconnect Association " in nvme_fc_match_disconn_ls()
1617 * Actual Processing routine for received FC-NVME LS Requests from the LLD
1704 * upon the reception of a NVME LS request.
1706 * The nvme-fc layer will copy payload to an internal structure for
1812 /* *********************** NVME Ctrl Routines **************************** */
1905 * @req:IO request from nvme fc to driver
1937 * The current linux implementation of a nvme controller in nvme_fc_fcpio_done()
1944 * This affects the FC-NVME implementation in two ways: in nvme_fc_fcpio_done()
1949 * 2) The FC-NVME implementation requires that delivery of in nvme_fc_fcpio_done()
1950 * ERSP completions are to go back to the nvme layer in order in nvme_fc_fcpio_done()
1952 * be "in order" for the nvme layer. As the nvme layer in in nvme_fc_fcpio_done()
1957 * As the core nvme layer in linux currently does not look at in nvme_fc_fcpio_done()
1964 * detected fashion unrelated to the nvme completion status, in nvme_fc_fcpio_done()
1967 * Per FC-NVME spec, failure of an individual command requires in nvme_fc_fcpio_done()
1982 "NVME-FC{%d}: io failed due to lldd error %d\n", in nvme_fc_fcpio_done()
2014 "NVME-FC{%d}: io failed due to bad transfer " in nvme_fc_fcpio_done()
2036 "NVME-FC{%d}: io failed due to bad NVMe_ERSP: " in nvme_fc_fcpio_done()
2054 "NVME-FC{%d}: io failed due to odd NVMe_xRSP iu " in nvme_fc_fcpio_done()
2257 * a native NVME sqe/cqe. More reasonable if FC-NVME IU payload in nvme_fc_init_queue()
2421 * All accesses from nvme core layer done - can now free the
2549 "NVME-FC{%d}: transport association event: %s\n", in nvme_fc_error_recovery()
2552 "NVME-FC{%d}: resetting controller\n", ctrl->cnum); in nvme_fc_error_recovery()
2569 "NVME-FC{%d.%d}: io timeout: opcode %d fctype %d w10/11: " in nvme_fc_timeout()
2678 /* format the FC-NVME CMD IU and fcp_req */ in nvme_fc_start_fcp_op()
2701 * as well as those by FC-NVME spec. in nvme_fc_start_fcp_op()
2707 * format SQE DPTR field per FC-NVME rules: in nvme_fc_start_fcp_op()
2798 * nvme core doesn't quite treat the rq opaquely. Commands such in nvme_fc_queue_rq()
3065 "NVME-FC{%d}: create association : host wwpn 0x%016llx " in nvme_fc_create_association()
3115 /* FC-NVME does not have other data in the capsule */ in nvme_fc_create_association()
3123 /* FC-NVME supports normal SGL Data Block Descriptors */ in nvme_fc_create_association()
3170 /* send a Disconnect(association) LS to fc-nvme target */ in nvme_fc_create_association()
3224 * send a Disconnect(association) LS to fc-nvme target in nvme_fc_delete_association()
3288 "NVME-FC{%d}: reset: Reconnect attempt failed (%d)\n", in nvme_fc_reconnect_or_delete()
3298 "NVME-FC{%d}: Reconnect attempt in %ld " in nvme_fc_reconnect_or_delete()
3309 "NVME-FC{%d}: reconnect failure\n", in nvme_fc_reconnect_or_delete()
3313 "NVME-FC{%d}: Max reconnect attempts " in nvme_fc_reconnect_or_delete()
3318 "NVME-FC{%d}: dev_loss_tmo (%d) expired " in nvme_fc_reconnect_or_delete()
3340 "NVME-FC{%d}: error_recovery: Couldn't change state " in nvme_fc_reset_ctrl_work()
3346 "NVME-FC{%d}: failed to schedule connect " in nvme_fc_reset_ctrl_work()
3384 "NVME-FC{%d}: controller connect complete\n", in nvme_fc_connect_ctrl_work()
3529 /* at this point, teardown path changes to ref counting on nvme ctrl */ in nvme_fc_init_ctrl()
3538 "NVME-FC{%d}: failed to init ctrl state\n", ctrl->cnum); in nvme_fc_init_ctrl()
3544 "NVME-FC{%d}: failed to schedule initial connect\n", in nvme_fc_init_ctrl()
3552 "NVME-FC{%d}: new ctrl: NQN \"%s\"\n", in nvme_fc_init_ctrl()
3565 /* initiate nvme ctrl ref counting teardown */ in nvme_fc_init_ctrl()
3882 * added to by NVME into a new standalone FC class. The SCSI in nvme_fc_init_module()
3883 * and NVME protocols and their devices would be under this in nvme_fc_init_module()
3887 * specifically for nvme probe events, start by creating the in nvme_fc_init_module()
3933 "NVME-FC{%d}: transport unloading: deleting ctrl\n", in nvme_fc_delete_controllers()