July 2014 Archives by author

• Messages sorted by: [ thread ] [ subject ] [ date ]
• More info on this list...

Starting: Tue Jul 1 07:53:01 PDT 2014
Ending: Tue Jul 29 13:31:36 PDT 2014
Messages: 50

• [PATCH] NVMe: Correctly handle IOCTL_SUBMIT_IO when cpus > online queues   Sam Bradshaw (sbradshaw)
• [PATCH v10] NVMe: Convert to blk-mq   Jens Axboe
• [PATCH v10] NVMe: Convert to blk-mq   Matias Bjorling
• [PATCH v10] Convert NVMe driver to blk-mq   Matias Bjørling
• [PATCH v10] NVMe: Convert to blk-mq   Matias Bjørling
• [PATCH v11] Convert NVMe driver to blk-mq   Matias Bjørling
• [PATCH v11] NVMe: Convert to blk-mq   Matias Bjørling
• [PATCH] NVMe: Correctly handle IOCTL_SUBMIT_IO when cpus > online queues   Sam Bradshaw
• [PATCH v2] NVMe: Correctly handle IOCTL_SUBMIT_IO when cpus > online queues   Sam Bradshaw
• NVME Kernel Panic due to nvme_free_queue running from call_rcu   Keith Busch
• [PATCH] NVMe: Write CC before calling enable.   Keith Busch
• NVM Express Format   Keith Busch
• [PATCH] NVMe: Call nvme_free_queue directly   Keith Busch
• [PATCH 1/2] block: Implement support for write zeros   Keith Busch
• [PATCH 2/2] NVMe: Implement WRITE_ZEROS support   Keith Busch
• NVME User Installation   Keith Busch
• [PATCH 1/1] Replace the dma_alloc_coherent() with dma_zalloc_coherent()   Keith Busch
• [PATCH] NVMe: Fix filesystem sync deadlock on removal   Keith Busch
• [PATCH] NVMe: PCI error handling code   Keith Busch
• NVME User Installation   Keith Busch
• [PATCH 1/1] If device hotplug out, controller status become 0xFFFF_FFFF 1. Controller fatal status become true in nvme_kthread() 2. Ready bit will not be reset to 0 in nvme_wait_ready() for controller disable above two scenarios controller status data is not a valid data, since device/controller is already removed (hotplug)   Keith Busch
• [PATCH] NVMe: Correctly handle IOCTL_SUBMIT_IO when cpus > online queues   Keith Busch
• NVMe: Invalid controller status value, device hotplug out   J Freyensee
• Compiling the latest linux-nvme kernel   Jay Freyensee
• [PATCH v10] NVMe: Convert to blk-mq   Christoph Hellwig
• [PATCH] NVMe: Add shutdown timeout as module parameter.   Dan McLeran
• [PATCH] NVMe: Write CC before calling enable.   Dan McLeran
• [PATCH] NVMe: Write CC before calling enable.   Dan McLeran
• NVME Kernel Panic due to nvme_free_queue running from call_rcu   Matthew Minter
• NVME Kernel Panic due to nvme_free_queue running from call_rcu   Matthew Minter
• NVM Express Format   Indraneel Mukherjee
• [PATCH 1/1] NVMe I/O queue depth change to module parameter   Mundu
• [PATCH 1/1] Replace the dma_alloc_coherent() with dma_zalloc_coherent()   Mundu
• NVMe: Invalid controller status value, device hotplug out   Mundu
• [PATCH 1/1] If device hotplug out, controller status become 0xFFFF_FFFF 1. Controller fatal status become true in nvme_kthread() 2. Ready bit will not be reset to 0 in nvme_wait_ready() for controller disable above two scenarios controller status data is not a valid data, since device/controller is already removed (hotplug)   Mundu
• NVMe Vendor Extension for Improved Virtualization   Rob Nelson
• [PATCH] NVMe: Write CC before calling enable.   Matthew Wilcox
• [PATCH 1/1] NVMe I/O queue depth change to module parameter   Matthew Wilcox
• [PATCH 1/1] Replace the dma_alloc_coherent() with dma_zalloc_coherent()   Matthew Wilcox
• [PATCH 1/1] NVMe I/O queue depth change to module parameter   Matthew Wilcox
• [PATCH 1/1] Replace the dma_alloc_coherent() with dma_zalloc_coherent()   Matthew Wilcox
• NVME User Installation   Ian Ziemba
• NVME User Installation   Ian Ziemba
• NVME User Installation   Ian Ziemba
• [PATCH 1/1] NVMe I/O queue depth change to module parameter   mundu agarwal
• [PATCH 1/1] Replace the dma_alloc_coherent() with dma_zalloc_coherent()   mundu agarwal
• [PATCH 1/1] Replace the dma_alloc_coherent() with dma_zalloc_coherent()   mundu agarwal
• [PATCH 1/1] NVMe I/O queue depth change to module parameter   mundu agarwal
• [PATCH 1/1] If device hotplug out, controller status become 0xFFFF_FFFF 1. Controller fatal status become true in nvme_kthread() 2. Ready bit will not be reset to 0 in nvme_wait_ready() for controller disable above two scenarios controller status data is not a valid data, since device/controller is already removed (hotplug)   mundu agarwal
• Linux-nvme Digest, Vol 28, Issue 17   mundu agarwal

Last message date: Tue Jul 29 13:31:36 PDT 2014
Archived on: Tue Jul 29 13:31:51 PDT 2014

• Messages sorted by: [ thread ] [ subject ] [ date ]
• More info on this list...