linux-toradex.git/drivers/nvme/host/Kconfig, branch v4.9.28

nvme: make NVME_RDMA depend on BLOCK

2016-09-11T21:41:49+00:00

Commit aa71987472a9 ("nvme: fabrics drivers don't need the nvme-pci
driver") removed the dependency on BLK_DEV_NVME, but the cdoe does
depend on the block layer (which used to be an implicit dependency
through BLK_DEV_NVME).

Otherwise you get various errors from the kbuild test robot random
config testing when that happens to hit a configuration with BLOCK
device support disabled.

Cc: Christoph Hellwig 
Cc: Jay Freyensee 
Cc: Sagi Grimberg 
Signed-off-by: Linus Torvalds

nvme: fabrics drivers don't need the nvme-pci driver

2016-08-19T11:22:28+00:00

So select the NVME_CORE symbol instead of depending on BLK_DEV_NVME.

Signed-off-by: Christoph Hellwig 
Reviewed-by: Jay Freyensee 
Signed-off-by: Sagi Grimberg

nvme-rdma: add a NVMe over Fabrics RDMA host driver

2016-07-08T14:38:49+00:00

This patch implements the RDMA host (initiator in SCSI speak) driver.  It
can be used to connect to remote NVMe over Fabrics controllers over
Infiniband, RoCE or iWarp, and uses the existing NVMe core driver as well
a the new fabrics library.

To connect to all NVMe over Fabrics controller reachable on a given taget
port using RDMA/CM use the following command:

	nvme connect-all -t rdma -a $IPADDR

This requires the latest version of nvme-cli with Fabrics support.

Signed-off-by: Jay Freyensee 
Signed-off-by: Ming Lin 
Signed-off-by: Sagi Grimberg 
Signed-off-by: Christoph Hellwig 
Reviewed-by: Steve Wise 
Tested-by: Steve Wise 
Signed-off-by: Jens Axboe

nvme-fabrics: add a generic NVMe over Fabrics library

2016-07-05T17:28:16+00:00

The NVMe over Fabrics library provides an interface for both transports
and the nvme core to handle fabrics specific commands and attributes
independent of the underlying transport.

In addition, the fabrics library adds a misc device interface that allow
actually creating a fabrics controller, as we can't just autodiscover
it like in the PCI case.  The nvme-cli utility has been enhanced to use
this interface to support fabric connect and discovery.

Signed-off-by: Armen Baloyan ,
Signed-off-by: Jay Freyensee ,
Signed-off-by: Ming Lin 
Signed-off-by: Sagi Grimberg 
Signed-off-by: Christoph Hellwig 
Reviewed-by: Keith Busch 
Signed-off-by: Jens Axboe

NVMe: small typo in section BLK_DEV_NVME_SCSI of host/Kconfig

2016-04-26T14:31:50+00:00

"as well as " is miss typed "as well a " in section
"config BLK_DEV_NVME_SCSI"

Signed-off-by: Wang Sheng-Hui 
Reviewed-by: Christoph Hellwig 
Signed-off-by: Jens Axboe

Merge branch 'for-4.6/drivers' of git://git.kernel.dk/linux-block

2016-03-19T00:13:31+00:00

Pull block driver updates from Jens Axboe:
 "This is the block driver pull request for this merge window.  It sits
  on top of for-4.6/core, that was just sent out.

  This contains:

   - A set of fixes for lightnvm.  One from Alan, fixing an overflow,
     and the rest from the usual suspects, Javier and Matias.

   - A set of fixes for nbd from Markus and Dan, and a fixup from Arnd
     for correct usage of the signed 64-bit divider.

   - A set of bug fixes for the Micron mtip32xx, from Asai.

   - A fix for the brd discard handling from Bart.

   - Update the maintainers entry for cciss, since that hardware has
     transferred ownership.

   - Three bug fixes for bcache from Eric Wheeler.

   - Set of fixes for xen-blk{back,front} from Jan and Konrad.

   - Removal of the cpqarray driver.  It has been disabled in Kconfig
     since 2013, and we were initially scheduled to remove it in 3.15.

   - Various updates and fixes for NVMe, with the most important being:

        - Removal of the per-device NVMe thread, replacing that with a
          watchdog timer instead. From Christoph.

        - Exposing the namespace WWID through sysfs, from Keith.

        - Set of cleanups from Ming Lin.

        - Logging the controller device name instead of the underlying
          PCI device name, from Sagi.

        - And a bunch of fixes and optimizations from the usual suspects
          in this area"

* 'for-4.6/drivers' of git://git.kernel.dk/linux-block: (49 commits)
  NVMe: Expose ns wwid through single sysfs entry
  drivers:block: cpqarray clean up
  brd: Fix discard request processing
  cpqarray: remove it from the kernel
  cciss: update MAINTAINERS
  NVMe: Remove unused sq_head read in completion path
  bcache: fix cache_set_flush() NULL pointer dereference on OOM
  bcache: cleaned up error handling around register_cache()
  bcache: fix race of writeback thread starting before complete initialization
  NVMe: Create discard zero quirk white list
  nbd: use correct div_s64 helper
  mtip32xx: remove unneeded variable in mtip_cmd_timeout()
  lightnvm: generalize rrpc ppa calculations
  lightnvm: remove struct nvm_dev->total_blocks
  lightnvm: rename ->nr_pages to ->nr_sects
  lightnvm: update closed list outside of intr context
  xen/blback: Fit the important information of the thread in 17 characters
  lightnvm: fold get bb tbl when using dual/quad plane mode
  lightnvm: fix up nonsensical configure overrun checking
  xen-blkback: advertise indirect segment support earlier
  ...

nvme: split pci module out of core module

2016-02-10T21:22:38+00:00

NVMe over Fabrics drivers are going to reuse the core,
so splits nvme.ko into 2 modules:

nvme-core.ko: the core part
nvme.ko: the PCI driver

Export symbols from nvme-core.ko.

Reviewed-by: Christoph Hellwig 
Signed-off-by: Ming Lin 
Signed-off-by: Jens Axboe

nvme: fix Kconfig description for BLK_DEV_NVME_SCSI

2016-02-09T17:21:22+00:00

Signed-off-by: Christoph Hellwig 
Signed-off-by: Jens Axboe

nvme: make SG_IO support optional

2016-01-12T20:30:16+00:00

Translation SCSI commands to NVMe commands is rather pointless in general
as applications must not expext to be able to use SCSI commands on a
generic block device.

Make the huge translation layer optional and hope no one will ever enable
it in the future.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Jens Axboe

NVMe: Add explicit block config dependency

2015-10-12T17:43:22+00:00

The nvme driver was moved from drivers/block, losing our implicit
dependency on CONFIG_BLOCK. This makes it an explicit driver dependency.

Reported-by: Jim Davis 
Signed-off-by: Keith Busch 
Reviewed-by: Christoph Hellwig 
Signed-off-by: Jens Axboe