xref: /OK3568_Linux_fs/kernel/drivers/nvme/host/Kconfig (revision 4882a59341e53eb6f0b4789bf948001014eff981)
1*4882a593Smuzhiyun# SPDX-License-Identifier: GPL-2.0-only
2*4882a593Smuzhiyunconfig NVME_CORE
3*4882a593Smuzhiyun	tristate
4*4882a593Smuzhiyun	select BLK_DEV_INTEGRITY_T10 if BLK_DEV_INTEGRITY
5*4882a593Smuzhiyun
6*4882a593Smuzhiyunconfig BLK_DEV_NVME
7*4882a593Smuzhiyun	tristate "NVM Express block device"
8*4882a593Smuzhiyun	depends on PCI && BLOCK
9*4882a593Smuzhiyun	select NVME_CORE
10*4882a593Smuzhiyun	help
11*4882a593Smuzhiyun	  The NVM Express driver is for solid state drives directly
12*4882a593Smuzhiyun	  connected to the PCI or PCI Express bus.  If you know you
13*4882a593Smuzhiyun	  don't have one of these, it is safe to answer N.
14*4882a593Smuzhiyun
15*4882a593Smuzhiyun	  To compile this driver as a module, choose M here: the
16*4882a593Smuzhiyun	  module will be called nvme.
17*4882a593Smuzhiyun
18*4882a593Smuzhiyunconfig NVME_MULTIPATH
19*4882a593Smuzhiyun	bool "NVMe multipath support"
20*4882a593Smuzhiyun	depends on NVME_CORE
21*4882a593Smuzhiyun	help
22*4882a593Smuzhiyun	   This option enables support for multipath access to NVMe
23*4882a593Smuzhiyun	   subsystems.  If this option is enabled only a single
24*4882a593Smuzhiyun	   /dev/nvmeXnY device will show up for each NVMe namespaces,
25*4882a593Smuzhiyun	   even if it is accessible through multiple controllers.
26*4882a593Smuzhiyun
27*4882a593Smuzhiyunconfig NVME_HWMON
28*4882a593Smuzhiyun	bool "NVMe hardware monitoring"
29*4882a593Smuzhiyun	depends on (NVME_CORE=y && HWMON=y) || (NVME_CORE=m && HWMON)
30*4882a593Smuzhiyun	help
31*4882a593Smuzhiyun	  This provides support for NVMe hardware monitoring. If enabled,
32*4882a593Smuzhiyun	  a hardware monitoring device will be created for each NVMe drive
33*4882a593Smuzhiyun	  in the system.
34*4882a593Smuzhiyun
35*4882a593Smuzhiyunconfig NVME_FABRICS
36*4882a593Smuzhiyun	tristate
37*4882a593Smuzhiyun
38*4882a593Smuzhiyunconfig NVME_RDMA
39*4882a593Smuzhiyun	tristate "NVM Express over Fabrics RDMA host driver"
40*4882a593Smuzhiyun	depends on INFINIBAND && INFINIBAND_ADDR_TRANS && BLOCK
41*4882a593Smuzhiyun	select NVME_CORE
42*4882a593Smuzhiyun	select NVME_FABRICS
43*4882a593Smuzhiyun	select SG_POOL
44*4882a593Smuzhiyun	help
45*4882a593Smuzhiyun	  This provides support for the NVMe over Fabrics protocol using
46*4882a593Smuzhiyun	  the RDMA (Infiniband, RoCE, iWarp) transport.  This allows you
47*4882a593Smuzhiyun	  to use remote block devices exported using the NVMe protocol set.
48*4882a593Smuzhiyun
49*4882a593Smuzhiyun	  To configure a NVMe over Fabrics controller use the nvme-cli tool
50*4882a593Smuzhiyun	  from https://github.com/linux-nvme/nvme-cli.
51*4882a593Smuzhiyun
52*4882a593Smuzhiyun	  If unsure, say N.
53*4882a593Smuzhiyun
54*4882a593Smuzhiyunconfig NVME_FC
55*4882a593Smuzhiyun	tristate "NVM Express over Fabrics FC host driver"
56*4882a593Smuzhiyun	depends on BLOCK
57*4882a593Smuzhiyun	depends on HAS_DMA
58*4882a593Smuzhiyun	select NVME_CORE
59*4882a593Smuzhiyun	select NVME_FABRICS
60*4882a593Smuzhiyun	select SG_POOL
61*4882a593Smuzhiyun	help
62*4882a593Smuzhiyun	  This provides support for the NVMe over Fabrics protocol using
63*4882a593Smuzhiyun	  the FC transport.  This allows you to use remote block devices
64*4882a593Smuzhiyun	  exported using the NVMe protocol set.
65*4882a593Smuzhiyun
66*4882a593Smuzhiyun	  To configure a NVMe over Fabrics controller use the nvme-cli tool
67*4882a593Smuzhiyun	  from https://github.com/linux-nvme/nvme-cli.
68*4882a593Smuzhiyun
69*4882a593Smuzhiyun	  If unsure, say N.
70*4882a593Smuzhiyun
71*4882a593Smuzhiyunconfig NVME_TCP
72*4882a593Smuzhiyun	tristate "NVM Express over Fabrics TCP host driver"
73*4882a593Smuzhiyun	depends on INET
74*4882a593Smuzhiyun	depends on BLOCK
75*4882a593Smuzhiyun	select NVME_CORE
76*4882a593Smuzhiyun	select NVME_FABRICS
77*4882a593Smuzhiyun	select CRYPTO
78*4882a593Smuzhiyun	select CRYPTO_CRC32C
79*4882a593Smuzhiyun	help
80*4882a593Smuzhiyun	  This provides support for the NVMe over Fabrics protocol using
81*4882a593Smuzhiyun	  the TCP transport.  This allows you to use remote block devices
82*4882a593Smuzhiyun	  exported using the NVMe protocol set.
83*4882a593Smuzhiyun
84*4882a593Smuzhiyun	  To configure a NVMe over Fabrics controller use the nvme-cli tool
85*4882a593Smuzhiyun	  from https://github.com/linux-nvme/nvme-cli.
86*4882a593Smuzhiyun
87*4882a593Smuzhiyun	  If unsure, say N.
88