1. 10 10月, 2015 11 次提交
  2. 01 10月, 2015 1 次提交
  3. 24 9月, 2015 1 次提交
  4. 26 8月, 2015 1 次提交
  5. 20 8月, 2015 2 次提交
  6. 19 8月, 2015 3 次提交
  7. 18 8月, 2015 1 次提交
    • K
      NVMe: Set queue max segments · e824410f
      Keith Busch 提交于
      This sets the queue's max segment size to match the device's
      capabilities. The default of 128 is usable until a device's transfer
      capability exceeds 512k, assuming a device page size of 4k. Many nvme
      devices exceed that transfer limit, so this lets the block layer know what
      kind of commands it to allow to form rather than unnecessarily split them.
      
      One additional segment is added to account for a transfer that may start
      in the middle of a page.
      Signed-off-by: NKeith Busch <keith.busch@intel.com>
      Reviewed-by: NChristoph Hellwig <hch@lst.de>
      Signed-off-by: NJens Axboe <axboe@fb.com>
      e824410f
  8. 22 7月, 2015 1 次提交
  9. 21 7月, 2015 2 次提交
  10. 17 7月, 2015 1 次提交
  11. 16 7月, 2015 1 次提交
  12. 02 7月, 2015 1 次提交
  13. 28 6月, 2015 6 次提交
  14. 20 6月, 2015 1 次提交
  15. 17 6月, 2015 1 次提交
  16. 06 6月, 2015 3 次提交
  17. 02 6月, 2015 1 次提交
    • K
      NVMe: Remove hctx reliance for multi-namespace · 42483228
      Keith Busch 提交于
      The driver needs to track shared tags to support multiple namespaces
      that may be dynamically allocated or deleted. Relying on the first
      request_queue's hctx's is not appropriate as we cannot clear outstanding
      tags for all namespaces using this handle, nor can the driver easily track
      all request_queue's hctx as namespaces are attached/detached. Instead,
      this patch uses the nvme_dev's tagset to get the shared tag resources
      instead of through a request_queue hctx.
      Signed-off-by: NKeith Busch <keith.busch@intel.com>
      Signed-off-by: NJens Axboe <axboe@fb.com>
      42483228
  18. 30 5月, 2015 2 次提交