| /Linux-v6.1/drivers/nvme/host/ |
| D | Kconfig | 16 module will be called nvme.
19 bool "NVMe multipath support"
22 This option enables support for multipath access to NVMe
24 /dev/nvmeXnY device will show up for each NVMe namespace,
28 bool "NVMe verbose error reporting"
31 This option enables verbose reporting for NVMe errors. The
36 bool "NVMe hardware monitoring"
39 This provides support for NVMe hardware monitoring. If enabled,
40 a hardware monitoring device will be created for each NVMe drive
53 This provides support for the NVMe over Fabrics protocol using
[all …]
|
| D | Makefile | 5 obj-$(CONFIG_NVME_CORE) += nvme-core.o
6 obj-$(CONFIG_BLK_DEV_NVME) += nvme.o
7 obj-$(CONFIG_NVME_FABRICS) += nvme-fabrics.o
8 obj-$(CONFIG_NVME_RDMA) += nvme-rdma.o
9 obj-$(CONFIG_NVME_FC) += nvme-fc.o
10 obj-$(CONFIG_NVME_TCP) += nvme-tcp.o
11 obj-$(CONFIG_NVME_APPLE) += nvme-apple.o
13 nvme-core-y += core.o ioctl.o
14 nvme-core-$(CONFIG_NVME_VERBOSE_ERRORS) += constants.o
15 nvme-core-$(CONFIG_TRACING) += trace.o
[all …]
|
| D | fabrics.c | 3 * NVMe over Fabrics common host code.
13 #include "nvme.h"
99 * @ctrl: Host NVMe controller instance which we got the address
125 * nvmf_reg_read32() - NVMe Fabrics "Property Get" API function.
126 * @ctrl: Host NVMe controller instance maintaining the admin
128 * the allocated NVMe controller resource on the target system.
130 * register (see the fabrics section of the NVMe standard).
135 * from an NVMe controller on the target system.
138 * NVMe fabrics space.)
142 * > 0: NVMe error status code
[all …]
|
| D | fabrics.h | 3 * NVMe over Fabrics common host code.
79 * on adding a NVMe controller.
81 * better description) that will be used by an NVMe controller
84 * in the NVMe specification, "NVMe Qualified Names").
89 * @host_traddr: A transport-specific field identifying the NVME host port
91 * @host_iface: A transport-specific field identifying the NVME host
98 * @host: Virtual NVMe host, contains the NQN and Host ID.
142 * fabric implementation of NVMe fabrics.
146 * @name: Name of the NVMe fabric driver implementation.
148 * when adding a new NVMe controller.
[all …]
|
| D | fc.c | 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
[all …]
|
| D | trace.h | 8 #define TRACE_SYSTEM nvme
13 #include <linux/nvme.h>
17 #include "nvme.h"
75 TP_printk("nvme%d: %sqid=%d, cmdid=%u, nsid=%u, flags=0x%x, meta=0x%x, cmd=(%s %s)",
108 TP_printk("nvme%d: %sqid=%d, cmdid=%u, res=%#llx, retries=%u, flags=0x%x, status=%#x",
128 TP_printk("nvme%d: NVME_AEN=%#08x [%s]",
161 TP_printk("nvme%d: %sqid=%d, head=%u, tail=%u",
|
| /Linux-v6.1/drivers/nvme/target/ |
| D | Kconfig | 4 tristate "NVMe Target support"
10 This enabled target side support for the NVMe protocol, that is
11 it allows the Linux kernel to implement NVMe subsystems and
12 controllers and export Linux block devices as NVMe namespaces.
16 To configure the NVMe target you probably want to use the nvmetcli
20 bool "NVMe Target Passthrough support"
24 This enables target side NVMe passthru controller support for the
25 NVMe Over Fabrics protocol. It allows for hosts to manage and
26 directly access an actual NVMe controller residing on the target
32 tristate "NVMe loopback device support"
[all …]
|
| D | Makefile | 6 obj-$(CONFIG_NVME_TARGET_LOOP) += nvme-loop.o
9 obj-$(CONFIG_NVME_TARGET_FCLOOP) += nvme-fcloop.o
17 nvme-loop-y += loop.o
20 nvme-fcloop-y += fcloop.o
|
| /Linux-v6.1/Documentation/devicetree/bindings/nvme/ |
| D | apple,nvme-ans.yaml | 4 $id: http://devicetree.org/schemas/nvme/apple,nvme-ans.yaml#
16 - apple,t8103-nvme-ans2
17 - apple,t6000-nvme-ans2
18 - const: apple,nvme-ans2
22 - description: NVMe and NVMMU registers
27 - const: nvme
37 - description: power domain for the NVMe controller.
38 - description: power domain for the first PCIe bus connecting the NVMe
41 connecting the NVMe controller to the storage modules.
68 const: apple,t8103-nvme-ans2
[all …]
|
| /Linux-v6.1/include/linux/ |
| D | nvme-tcp.h | 3 * NVMe over Fabrics TCP protocol header.
10 #include <linux/nvme.h>
56 * struct nvme_tcp_hdr - nvme tcp pdu common header
73 * struct nvme_tcp_icreq_pdu - nvme tcp initialize connection request pdu
91 * struct nvme_tcp_icresp_pdu - nvme tcp initialize connection response pdu
109 * struct nvme_tcp_term_pdu - nvme tcp terminate connection pdu
123 * struct nvme_tcp_cmd_pdu - nvme tcp command capsule pdu
126 * @cmd: nvme command
134 * struct nvme_tcp_rsp_pdu - nvme tcp response capsule pdu
137 * @hdr: nvme-tcp generic header
[all …]
|
| D | nvme-fc-driver.h | 14 * ********************** FC-NVME LS API ********************
16 * Data structures used by both FC-NVME hosts and FC-NVME
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
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
80 * Used by the LLDD to pass the nvme-fc transport (host)
86 * or nvme-fc layer via the xxx_rcv_ls_req() transport routines.
[all …]
|
| D | nvme-fc.h | 7 * This file contains definitions relative to FC-NVME-2 r1.08
19 /* FC-NVME Cmd IU Flags */
114 /* FC-NVME Link Services - LS cmd values (w0 bits 31:24) */
125 /* FC-NVME Link Service Descriptors */
162 /* FC-NVME LS RJT reason_code values */
195 /* FC-NVME LS RJT reason_explanation values */
423 * Note: FC-NVME-2 standard requires a "0x" prefix.
|
| /Linux-v6.1/drivers/scsi/qla2xxx/ |
| D | qla_nvme.c | 9 #include <linux/nvme.h>
10 #include <linux/nvme-fc.h>
27 "%s: Not registering target since Host NVME is not enabled\n", in qla_nvme_register_remote()
91 /* Allocate a queue for NVMe traffic */
146 struct srb_iocb *nvme; in qla_nvme_release_fcp_cmd_kref() local
152 nvme = &sp->u.iocb_cmd; in qla_nvme_release_fcp_cmd_kref()
153 fd = nvme->u.nvme.desc; in qla_nvme_release_fcp_cmd_kref()
159 fd->rcv_rsplen = le16_to_cpu(nvme->u.nvme.rsp_pyld_len); in qla_nvme_release_fcp_cmd_kref()
176 struct srb_iocb *nvme = &sp->u.iocb_cmd; in qla_nvme_ls_unmap() local
179 dma_unmap_single(&ha->pdev->dev, nvme->u.nvme.cmd_dma, in qla_nvme_ls_unmap()
[all …]
|
| D | qla_nvme.h | 11 #include <linux/nvme-fc-driver.h>
42 #define COMMAND_NVME 0x88 /* Command Type FC-NVMe IOCB */
54 __le16 nvme_rsp_dsd_len; /* NVMe RSP DSD length */
106 #define PT_LS4_UNSOL 0x56 /* pass-up unsolicited rec FC-NVMe request */
|
| /Linux-v6.1/drivers/scsi/lpfc/ |
| D | lpfc_nvme.c | 54 /* NVME initiator-based functions */
108 * NVME qidx == 0 is the admin queue, so both admin queue in lpfc_nvme_create_queue()
179 * @remoteport: Pointer to an nvme transport remoteport instance.
181 * This is a template downcall. NVME transport calls this function
213 * transport. Remove the ndlp reference for the NVME transport before in lpfc_nvme_remoteport_delete()
231 * NVME and SCSI rport unregister requests are complete. If the vport in lpfc_nvme_remoteport_delete()
242 * lpfc_nvme_handle_lsreq - Process an unsolicited NVME LS request
244 * @axchg: pointer to exchange context for the NVME LS request
246 * This routine is used for processing an asychronously received NVME LS
248 * to the nvme-fc transport via nvme_fc_rcv_ls_req().
[all …]
|
| D | lpfc_disc.h | 111 #define NLP_NVME_TARGET 0x20 /* entry is a NVME Target */
112 #define NLP_NVME_INITIATOR 0x40 /* entry is a NVME Initiator */
113 #define NLP_NVME_DISCOVERY 0x80 /* entry has NVME disc srvc */
117 * FCP (0x8) and NVME (0x28)
122 #define NLP_FC4_NVME 0x2 /* FC4 TYPE NVME (value x28) */
135 u8 nlp_nvme_info; /* NVME NSLER Support */
137 #define NLP_NVME_NSLER 0x1 /* NVME NSLER device */
142 struct lpfc_nvme_rport *nrport; /* nvme transport rport struct. */
159 uint32_t nvme_fb_size; /* NVME target's supported byte cnt */
|
| D | lpfc_nvme.h | 24 #include <linux/nvme.h>
25 #include <linux/nvme-fc-driver.h>
26 #include <linux/nvme-fc.h>
47 /* Declare nvme-based local and remote port definitions. */
80 * set NVME LS request timeouts to 30s. It is larger than the 2*R_A_TOV
97 /* Used for NVME Target */
|
| D | lpfc_nvmet.c | 76 /* Setup WQE templates for NVME IOs */
285 * transmission of an NVME LS response.
292 * used to send the NVME LS RSP.
338 * lock held. This function is the completion handler for NVME LS commands
550 * to FCP command is passed to NVME Layer. in lpfc_nvmet_ktime()
552 * off to NVME Layer to Driver receives a Command op in lpfc_nvmet_ktime()
553 * from NVME Layer. in lpfc_nvmet_ktime()
555 * from NVME Layer to Command is put on WQ. in lpfc_nvmet_ktime()
559 * Command cmpl is passed to NVME Layer. in lpfc_nvmet_ktime()
560 * Segment 6 - Time from Command cmpl is passed to NVME in lpfc_nvmet_ktime()
[all …]
|
| D | lpfc_logmsg.h | 43 #define LOG_NVME 0x00100000 /* NVME general events. */
44 #define LOG_NVME_DISC 0x00200000 /* NVME Discovery/Connect events. */
45 #define LOG_NVME_ABTS 0x00400000 /* NVME ABTS events. */
46 #define LOG_NVME_IOERR 0x00800000 /* NVME IO Error events. */
|
| /Linux-v6.1/Documentation/fault-injection/ |
| D | nvme-fault-injection.rst | 1 NVMe Fault Injection
8 Status can be found in include/linux/nvme.h
10 Following examples show how to inject an error into the nvme.
42 nvme_process_cq+0xe7/0x1d0 [nvme]
43 nvme_irq+0x1e/0x40 [nvme]
130 nvme reset /dev/nvme0
134 After NVMe controller reset, the reinitialization may or may not succeed.
139 nvme nvme0: resetting controller
149 nvme_irq+0x129/0x280 [nvme]
177 nvme nvme0: Could not set queue count (16385)
[all …]
|
| /Linux-v6.1/drivers/nvme/ |
| D | Kconfig | 2 menu "NVME Support"
4 source "drivers/nvme/common/Kconfig"
5 source "drivers/nvme/host/Kconfig"
6 source "drivers/nvme/target/Kconfig"
|
| /Linux-v6.1/Documentation/driver-api/pci/ |
| D | p2pdma.rst | 46 For example, in the NVMe Target Copy Offload implementation:
48 * The NVMe PCI driver is both a client, provider and orchestrator
54 can DMA directly to the memory exposed by the NVMe device.
55 * The NVMe Target driver (nvmet) can orchestrate the data from the RNIC
56 to the P2P memory (CMB) and then to the NVMe device (and vice versa).
62 then the NVMe Target could use the RNIC's memory instead of the CMB
63 in cases where the NVMe cards in use do not have CMB support.
106 example, the NVMe Target driver creates a list including the namespace
|
| /Linux-v6.1/arch/s390/kernel/ |
| D | ipl.c | 44 #define IPL_NVME_STR "nvme"
50 #define DUMP_NVME_STR "nvme"
280 if (ipl_block.nvme.opt == IPL_PB0_NVME_OPT_DUMP) in get_ipl_type()
342 return sprintf(page, "%08ux\n", ipl_block.nvme.fid); in sys_ipl_device_show()
376 unsigned int size = ipl_block.nvme.scp_data_len; in ipl_nvme_scp_data_read()
377 void *scp_data = &ipl_block.nvme.scp_data; in ipl_nvme_scp_data_read()
411 /* NVMe ipl device attributes */
413 (unsigned long long)ipl_block.nvme.fid);
415 (unsigned long long)ipl_block.nvme.nsid);
417 (unsigned long long)ipl_block.nvme.bootprog);
[all …]
|
| /Linux-v6.1/drivers/scsi/mpt3sas/mpi/ |
| D | mpi2_pci.h | 25 * NVME Encapsulated Request.
26 * 07-22-18 02.00.03 Updted flags field for NVME Encapsulated req
49 * NVMe Encapsulated message
52 /*NVME Encapsulated Request Message */
91 /*NVMe Encapuslated Reply Message */
|
| /Linux-v6.1/drivers/nvme/common/ |
| D | Makefile | 5 obj-$(CONFIG_NVME_COMMON) += nvme-common.o
7 nvme-common-y += auth.o
|
