2016-06-21 16:04:20 +00:00
|
|
|
|
|
|
|
config NVME_TARGET
|
|
|
|
tristate "NVMe Target support"
|
|
|
|
depends on BLOCK
|
|
|
|
depends on CONFIGFS_FS
|
|
|
|
help
|
|
|
|
This enabled target side support for the NVMe protocol, that is
|
|
|
|
it allows the Linux kernel to implement NVMe subsystems and
|
|
|
|
controllers and export Linux block devices as NVMe namespaces.
|
|
|
|
You need to select at least one of the transports below to make this
|
|
|
|
functionality useful.
|
|
|
|
|
|
|
|
To configure the NVMe target you probably want to use the nvmetcli
|
|
|
|
tool from http://git.infradead.org/users/hch/nvmetcli.git.
|
|
|
|
|
2016-06-21 16:04:21 +00:00
|
|
|
config NVME_TARGET_LOOP
|
|
|
|
tristate "NVMe loopback device support"
|
|
|
|
depends on BLK_DEV_NVME
|
2016-07-07 09:01:26 +00:00
|
|
|
depends on CONFIGFS_FS
|
2016-06-21 16:04:21 +00:00
|
|
|
select NVME_TARGET
|
|
|
|
select NVME_FABRICS
|
|
|
|
select SG_POOL
|
|
|
|
help
|
|
|
|
This enables the NVMe loopback device support, which can be useful
|
|
|
|
to test NVMe host and target side features.
|
|
|
|
|
2016-06-21 16:04:20 +00:00
|
|
|
If unsure, say N.
|