diff options
author | Keith Busch <keith.busch@intel.com> | 2016-03-04 21:15:17 +0100 |
---|---|---|
committer | Jens Axboe <axboe@fb.com> | 2016-03-08 16:32:40 +0100 |
commit | 08095e70783f1d8296f858d37a9e1878f5da0623 (patch) | |
tree | ba47bfb1a2d003b81866879d63881ffb360ee273 /drivers/md | |
parent | nbd: use correct div_s64 helper (diff) | |
download | linux-08095e70783f1d8296f858d37a9e1878f5da0623.tar.xz linux-08095e70783f1d8296f858d37a9e1878f5da0623.zip |
NVMe: Create discard zero quirk white list
The NVMe specification does not require discarded blocks return zeroes on
read, but provides that behavior as a possibility. Some applications more
efficiently use an SSD if reads on discarded blocks were deterministically
zero, based on the "discard_zeroes_data" queue attribute.
There is no specification defined way to determine device behavior on
discarded blocks, so the driver always left the queue setting disabled. We
can only know behavior based on individual device models, so this patch
adds a flag to the NVMe "quirk" list that vendors may set if they know
their controller works that way. The patch also sets the new flag for one
such known device.
Signed-off-by: Keith Busch <keith.busch@intel.com>
Suggested-by: Artur Paszkiewicz <artur.paszkiewicz@intel.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de>
Reviewed-by: Sagi Grimberg <sagig@mellanox.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'drivers/md')
0 files changed, 0 insertions, 0 deletions