1. 21 12月, 2016 2 次提交
    • M
      nvme/pci: Fix whitespace problem · 9fa196e7
      Max Gurtovoy 提交于
      Convert to tabs and remove unneeded whitespaces.
      Signed-off-by: NMax Gurtovoy <maxg@mellanox.com>
      Signed-off-by: NChristoph Hellwig <hch@lst.de>
      9fa196e7
    • K
      nvme: simplify stripe quirk · e6282aef
      Keith Busch 提交于
      Some OEMs believe they own the Identify Controller vendor specific
      region and will repurpose it with their own values. While not common,
      we can't rely on the PCI VID:DID to tell use how to decode the field
      we reserved for this as the stripe size so we need to do something else
      for the list of devices using this quirk.
      
      The field was supposed to allow flexibility on the device's back-end
      striping, but it turned out that never materialized; the chunk is always
      the same as MDTS in the products subscribing to this quirk, so this
      patch removes the stripe_size field and sets the chunk to the max hw
      transfer size for the devices using this quirk.
      Signed-off-by: NKeith Busch <keith.busch@intel.com>
      Signed-off-by: NChristoph Hellwig <hch@lst.de>
      e6282aef
  2. 15 12月, 2016 2 次提交
  3. 14 12月, 2016 2 次提交
    • A
      nvme/pci: Log PCI_STATUS when the controller dies · d2a61918
      Andy Lutomirski 提交于
      When debugging nvme controller crashes, it's nice to know whether
      the controller died cleanly so that the failure is just reflected in
      CSTS, it died and put an error in PCI_STATUS, or whether it died so
      badly that it stopped responding to PCI configuration space reads.
      
      I've seen a failure that gives 0xffff in PCI_STATUS on a Samsung
      "SM951 NVMe SAMSUNG 256GB" with firmware "BXW75D0Q".
      Reviewed-by: NChristoph Hellwig <hch@lst.de>
      Signed-off-by: NAndy Lutomirski <luto@kernel.org>
      Reviewed-by: NKeith Busch <keith.busch@intel.com>
      
      Fixed up white space and hunk reject.
      Signed-off-by: NJens Axboe <axboe@fb.com>
      d2a61918
    • L
      Revert "nvme: add support for the Write Zeroes command" · cdb98c26
      Linus Torvalds 提交于
      This reverts commit 6d31e3ba.
      
      This causes bootup problems for me both on my laptop and my desktop.
      What they have in common is that they have NVMe disks with dm-crypt, but
      it's not the same controller, so it's not controller-specific.
      
      Jens does not see it on his machine (also NVMe), so it's presumably
      something that triggers just on bootup.  Possibly related to dm-crypt
      and the fact that I mark my luks volume with "allow-discards" in
      /etc/crypttab.
      
      It's 100% repeatable for me, which made it fairly straightforward to
      bisect the problem to this commit. Small mercies.
      
      So we don't know what the reason is yet, but the revert is needed to get
      things going again.
      Acked-by: NJens Axboe <axboe@fb.com>
      Cc: Chaitanya Kulkarni <chaitanya.kulkarni@hgst.com>
      Cc: Christoph Hellwig <hch@lst.de>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      cdb98c26
  4. 09 12月, 2016 1 次提交
    • C
      block: improve handling of the magic discard payload · f9d03f96
      Christoph Hellwig 提交于
      Instead of allocating a single unused biovec for discard requests, send
      them down without any payload.  Instead we allow the driver to add a
      "special" payload using a biovec embedded into struct request (unioned
      over other fields never used while in the driver), and overloading
      the number of segments for this case.
      
      This has a couple of advantages:
      
       - we don't have to allocate the bio_vec
       - the amount of special casing for discard requests in the block
         layer is significantly reduced
       - using this same scheme for other request types is trivial,
         which will be important for implementing the new WRITE_ZEROES
         op on devices where it actually requires a payload (e.g. SCSI)
       - we can get rid of playing games with the request length, as
         we'll never touch it and completions will work just fine
       - it will allow us to support ranged discard operations in the
         future by merging non-contiguous discard bios into a single
         request
       - last but not least it removes a lot of code
      
      This patch is the common base for my WIP series for ranges discards and to
      remove discard_zeroes_data in favor of always using REQ_OP_WRITE_ZEROES,
      so it would be good to get it in quickly.
      Signed-off-by: NChristoph Hellwig <hch@lst.de>
      Signed-off-by: NJens Axboe <axboe@fb.com>
      f9d03f96
  5. 06 12月, 2016 16 次提交
  6. 01 12月, 2016 3 次提交
  7. 30 11月, 2016 5 次提交
  8. 22 11月, 2016 1 次提交
  9. 17 11月, 2016 1 次提交
  10. 16 11月, 2016 1 次提交
  11. 14 11月, 2016 6 次提交