1. 28 2月, 2022 23 次提交
  2. 02 2月, 2022 3 次提交
  3. 27 1月, 2022 2 次提交
  4. 06 1月, 2022 1 次提交
  5. 23 12月, 2021 4 次提交
  6. 17 12月, 2021 3 次提交
  7. 08 12月, 2021 3 次提交
  8. 06 12月, 2021 1 次提交
    • N
      nvme: report write pointer for a full zone as zone start + zone len · 793fcab8
      Niklas Cassel 提交于
      The write pointer in NVMe ZNS is invalid for a zone in zone state full.
      The same also holds true for ZAC/ZBC.
      
      The current behavior for NVMe is to simply propagate the wp reported by
      the drive, even for full zones. Since the wp is invalid for a full zone,
      the wp reported by the drive may be any value.
      
      The way that the sd_zbc driver handles a full zone is to always report
      the wp as zone start + zone len, regardless of what the drive reported.
      null_blk also follows this convention.
      
      Do the same for NVMe, so that a BLKREPORTZONE ioctl reports the write
      pointer for a full zone in a consistent way, regardless of the interface
      of the underlying zoned block device.
      
      blkzone report before patch:
      start: 0x000040000, len 0x040000, cap 0x03e000, wptr 0xfffffffffffbfff8
      reset:0 non-seq:0, zcond:14(fu) [type: 2(SEQ_WRITE_REQUIRED)]
      
      blkzone report after patch:
      start: 0x000040000, len 0x040000, cap 0x03e000, wptr 0x040000 reset:0
      non-seq:0, zcond:14(fu) [type: 2(SEQ_WRITE_REQUIRED)]
      Signed-off-by: NNiklas Cassel <niklas.cassel@wdc.com>
      Reviewed-by: NKeith Busch <kbusch@kernel.org>
      Reviewed-by: NDamien Le Moal <damien.lemoal@opensource.wdc.com>
      Reviewed-by: NJohannes Thumshirn <johannes.thumshirn@wdc.com>
      Signed-off-by: NChristoph Hellwig <hch@lst.de>
      793fcab8