blob: 3a5b9d0576cb0f71a5bf22a34c905ae8dfc634fb [file] [log] [blame]
Christoph Hellwiga07b4972016-06-21 18:04:20 +02001
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
Christoph Hellwig3a85a5d2016-06-21 18:04:21 +020016config NVME_TARGET_LOOP
17 tristate "NVMe loopback device support"
Arnd Bergmann6eae8c42016-07-12 08:36:40 -070018 depends on NVME_TARGET
Christoph Hellwigaa719872016-08-18 11:16:36 -070019 select NVME_CORE
Christoph Hellwig3a85a5d2016-06-21 18:04:21 +020020 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
Christoph Hellwiga07b4972016-06-21 18:04:20 +020026 If unsure, say N.
Christoph Hellwig8f000ca2016-07-06 21:55:51 +090027
28config NVME_TARGET_RDMA
29 tristate "NVMe over Fabrics RDMA target support"
30 depends on INFINIBAND
Arnd Bergmann6eae8c42016-07-12 08:36:40 -070031 depends on NVME_TARGET
Christoph Hellwig8f000ca2016-07-06 21:55:51 +090032 help
33 This enables the NVMe RDMA target support, which allows exporting NVMe
34 devices over RDMA.
35
36 If unsure, say N.