Merge remote-tracking branch 'battery/for-next'
[deliverable/linux.git] / drivers / nvme / target / Kconfig
CommitLineData
a07b4970
CH
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
3a85a5de
CH
16config NVME_TARGET_LOOP
17 tristate "NVMe loopback device support"
6eae8c45 18 depends on NVME_TARGET
aa719874 19 select NVME_CORE
3a85a5de
CH
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
a07b4970 26 If unsure, say N.
8f000cac
CH
27
28config NVME_TARGET_RDMA
29 tristate "NVMe over Fabrics RDMA target support"
30 depends on INFINIBAND
6eae8c45 31 depends on NVME_TARGET
8f000cac
CH
32 help
33 This enables the NVMe RDMA target support, which allows exporting NVMe
34 devices over RDMA.
35
36 If unsure, say N.
This page took 0.036791 seconds and 5 git commands to generate.