Directory Files
.. 6
File Size
.admin-cmd.o.cmd 58 kB
.auth.o.cmd 58 kB
.built-in.a.cmd 123 B
.configfs.o.cmd 60 kB
.core.o.cmd 69 kB
.debugfs.o.cmd 58 kB
.discovery.o.cmd 58 kB
.fabrics-cmd-auth.o.cmd 58 kB
.fabrics-cmd.o.cmd 58 kB
.fc.o.cmd 58 kB
.fcloop.o.cmd 62 kB
.io-cmd-bdev.o.cmd 60 kB
.io-cmd-file.o.cmd 58 kB
.loop.o.cmd 68 kB
.modules.order.cmd 371 B
.nvme-fcloop.ko.cmd 315 B
.nvme-fcloop.mod.cmd 166 B
.nvme-fcloop.mod.o.cmd 50 kB
.nvme-fcloop.o.cmd 492 B
.nvme-loop.ko.cmd 307 B
.nvme-loop.mod.cmd 160 B
.nvme-loop.mod.o.cmd 50 kB
.nvme-loop.o.cmd 482 B
.nvmet-fc.ko.cmd 303 B
.nvmet-fc.mod.cmd 156 B
.nvmet-fc.mod.o.cmd 50 kB
.nvmet-fc.o.cmd 477 B
.nvmet-pci-epf.ko.cmd 323 B
.nvmet-pci-epf.mod.cmd 171 B
.nvmet-pci-epf.mod.o.cmd 50 kB
.nvmet-pci-epf.o.cmd 502 B
.nvmet-rdma.ko.cmd 311 B
.nvmet-rdma.mod.cmd 162 B
.nvmet-rdma.mod.o.cmd 50 kB
.nvmet-rdma.o.cmd 487 B
.nvmet-tcp.ko.cmd 307 B
.nvmet-tcp.mod.cmd 159 B
.nvmet-tcp.mod.o.cmd 50 kB
.nvmet-tcp.o.cmd 482 B
.nvmet.ko.cmd 291 B
.nvmet.mod.cmd 295 B
.nvmet.mod.o.cmd 50 kB
.nvmet.o.cmd 462 B
.passthru.o.cmd 62 kB
.pci-epf.o.cmd 62 kB
.pr.o.cmd 58 kB
.rdma.o.cmd 78 kB
.tcp.o.cmd 78 kB
.trace.o.cmd 59 kB
.zns.o.cmd 58 kB
Kconfig 3.9 kB
Makefile 872 B
admin-cmd.c 45 kB
admin-cmd.o 167 kB
auth.c 14 kB
auth.o 78 kB
built-in.a 8 B
configfs.c 62 kB
configfs.o 301 kB
core.c 51 kB
core.o 346 kB
debugfs.c 8.3 kB
debugfs.h 1.3 kB
debugfs.o 59 kB
discovery.c 12 kB
discovery.o 47 kB
fabrics-cmd-auth.c 20 kB
fabrics-cmd-auth.o 107 kB
fabrics-cmd.c 11 kB
fabrics-cmd.o 57 kB
fc.c 82 kB
fc.o 298 kB
fcloop.c 42 kB
fcloop.o 158 kB
io-cmd-bdev.c 12 kB
io-cmd-bdev.o 53 kB
io-cmd-file.c 9.2 kB
io-cmd-file.o 51 kB
loop.c 19 kB
loop.o 77 kB
modules.order 226 B
nvme-fcloop.ko 220 kB
nvme-fcloop.mod 29 B
nvme-fcloop.mod.c 475 B
nvme-fcloop.mod.o 3.3 kB
nvme-fcloop.o 223 kB
nvme-loop.ko 105 kB
nvme-loop.mod 27 B
nvme-loop.mod.c 481 B
nvme-loop.mod.o 3.3 kB
nvme-loop.o 106 kB
nvmet-fc.ko 418 kB
nvmet-fc.mod 25 B
nvmet-fc.mod.c 996 B
nvmet-fc.mod.o 7.3 kB
nvmet-fc.o 428 kB
nvmet-pci-epf.ko 325 kB
nvmet-pci-epf.mod 30 B
nvmet-pci-epf.mod.c 468 B
nvmet-pci-epf.mod.o 3.3 kB
nvmet-pci-epf.o 329 kB
nvmet-rdma.ko 341 kB
nvmet-rdma.mod 27 B
nvmet-rdma.mod.c 474 B
nvmet-rdma.mod.o 3.3 kB
nvmet-rdma.o 346 kB
nvmet-tcp.ko 321 kB
nvmet-tcp.mod 26 B
nvmet-tcp.mod.c 471 B
nvmet-tcp.mod.o 3.3 kB
nvmet-tcp.o 324 kB
nvmet.h 30 kB
nvmet.ko 2.0 MB
nvmet.mod 430 B
nvmet.mod.c 2.0 kB
nvmet.mod.o 15 kB
nvmet.o 2.1 MB
passthru.c 19 kB
passthru.o 75 kB
pci-epf.c 67 kB
pci-epf.o 240 kB
pr.c 30 kB
pr.o 135 kB
rdma.c 56 kB
rdma.o 250 kB
tcp.c 60 kB
tcp.o 234 kB
trace.c 12 kB
trace.h 4.8 kB
trace.o 41 kB
zns.c 17 kB
zns.o 64 kB

Linux v7.4-rc3 - target

# SPDX-License-Identifier: GPL-2.0-only

config NVME_TARGET
	tristate "NVMe Target support"
	depends on BLOCK
	select CONFIGFS_FS
	select NVME_KEYRING if NVME_TARGET_TCP_TLS
	select KEYS if NVME_TARGET_TCP_TLS
	select SGL_ALLOC
	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.

config NVME_TARGET_DEBUGFS
        bool "NVMe Target debugfs support"
	depends on NVME_TARGET
	help
	  This enables debugfs support to display the connected controllers
	  to each subsystem

	  If unsure, say N.

config NVME_TARGET_PASSTHRU
	bool "NVMe Target Passthrough support"
	depends on NVME_TARGET
	depends on NVME_CORE=y || NVME_CORE=NVME_TARGET
	help
	  This enables target side NVMe passthru controller support for the
	  NVMe Over Fabrics protocol. It allows for hosts to manage and
	  directly access an actual NVMe controller residing on the target
	  side, including executing Vendor Unique Commands.

	  If unsure, say N.

config NVME_TARGET_LOOP
	tristate "NVMe loopback device support"
	depends on 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.

	  If unsure, say N.

config NVME_TARGET_RDMA
	tristate "NVMe over Fabrics RDMA target support"
	depends on INFINIBAND && INFINIBAND_ADDR_TRANS
	depends on NVME_TARGET
	select SGL_ALLOC
	help
	  This enables the NVMe RDMA target support, which allows exporting NVMe
	  devices over RDMA.

	  If unsure, say N.

config NVME_TARGET_FC
	tristate "NVMe over Fabrics FC target driver"
	depends on NVME_TARGET
	depends on HAS_DMA
	select SGL_ALLOC
	help
	  This enables the NVMe FC target support, which allows exporting NVMe
	  devices over FC.

	  If unsure, say N.

config NVME_TARGET_FCLOOP
	tristate "NVMe over Fabrics FC Transport Loopback Test driver"
	depends on NVME_TARGET
	select NVME_FABRICS
	select SG_POOL
	depends on NVME_FC
	depends on NVME_TARGET_FC
	help
	  This enables the NVMe FC loopback test support, which can be useful
	  to test NVMe-FC transport interfaces.

	  If unsure, say N.

config NVME_TARGET_TCP
	tristate "NVMe over Fabrics TCP target support"
	depends on INET
	depends on NVME_TARGET
	help
	  This enables the NVMe TCP target support, which allows exporting NVMe
	  devices over TCP.

	  If unsure, say N.

config NVME_TARGET_TCP_TLS
	bool "NVMe over Fabrics TCP target TLS encryption support"
	depends on NVME_TARGET_TCP
	select NET_HANDSHAKE
	select TLS
	help
	  Enables TLS encryption for the NVMe TCP target using the netlink handshake API.

	  The TLS handshake daemon is available at
	  https://github.com/oracle/ktls-utils.

	  If unsure, say N.

config NVME_TARGET_AUTH
	bool "NVMe over Fabrics In-band Authentication in target side"
	depends on NVME_TARGET
	select NVME_AUTH
	help
	  This enables support for NVMe over Fabrics In-band Authentication in
	  target side.

	  If unsure, say N.

config NVME_TARGET_AUTH_DEBUG
	bool "NVMe over Fabrics In-band Authentication debug messages"
	depends on NVME_TARGET_AUTH
	help
	  This enables additional debug messages including the generated
	  DH-HMAC-CHAP secrets to help debugging authentication failures.

	  If unsure, say N.

config NVME_TARGET_PCI_EPF
	tristate "NVMe PCI Endpoint Function target support"
	depends on NVME_TARGET && PCI_ENDPOINT
	depends on NVME_CORE=y || NVME_CORE=NVME_TARGET
	help
	  This enables the NVMe PCI Endpoint Function target driver support,
	  which allows creating a NVMe PCI controller using an endpoint mode
	  capable PCI controller.

	  If unsure, say N.