Kconfig 2.6 KB

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