xref: /openbmc/linux/drivers/nvme/target/Kconfig (revision c0c74acb)
1
2config NVME_TARGET
3	tristate "NVMe Target support"
4	depends on BLOCK
5	depends on CONFIGFS_FS
6	help
7	  This enabled target side support for the NVMe protocol, that is
8	  it allows the Linux kernel to implement NVMe subsystems and
9	  controllers and export Linux block devices as NVMe namespaces.
10	  You need to select at least one of the transports below to make this
11	  functionality useful.
12
13	  To configure the NVMe target you probably want to use the nvmetcli
14	  tool from http://git.infradead.org/users/hch/nvmetcli.git.
15
16config NVME_TARGET_LOOP
17	tristate "NVMe loopback device support"
18	depends on NVME_TARGET
19	select NVME_CORE
20	select NVME_FABRICS
21	select SG_POOL
22	help
23	  This enables the NVMe loopback device support, which can be useful
24	  to test NVMe host and target side features.
25
26	  If unsure, say N.
27
28config NVME_TARGET_RDMA
29	tristate "NVMe over Fabrics RDMA target support"
30	depends on INFINIBAND
31	depends on NVME_TARGET
32	help
33	  This enables the NVMe RDMA target support, which allows exporting NVMe
34	  devices over RDMA.
35
36	  If unsure, say N.
37
38config NVME_TARGET_FC
39	tristate "NVMe over Fabrics FC target driver"
40	depends on NVME_TARGET
41	depends on HAS_DMA
42	help
43	  This enables the NVMe FC target support, which allows exporting NVMe
44	  devices over FC.
45
46	  If unsure, say N.
47
48config NVME_TARGET_FCLOOP
49	tristate "NVMe over Fabrics FC Transport Loopback Test driver"
50	depends on NVME_TARGET
51	select NVME_CORE
52	select NVME_FABRICS
53	select SG_POOL
54	depends on NVME_FC
55	depends on NVME_TARGET_FC
56	help
57	  This enables the NVMe FC loopback test support, which can be useful
58	  to test NVMe-FC transport interfaces.
59
60	  If unsure, say N.
61