diff options
author | James Smart <jsmart2021@gmail.com> | 2019-03-13 18:55:00 +0100 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2019-03-13 12:05:39 -0600 |
commit | 9f7d8ae2f79479ce13d987c8f3b1500b8937fc5d (patch) | |
tree | 22e4aa1b3354b7d721a5908c96949f2491dfeddf /scripts/package | |
parent | d11de63f2b519f0a162b834013b6d3a46dbf3886 (diff) | |
download | linux-9f7d8ae2f79479ce13d987c8f3b1500b8937fc5d.tar.bz2 |
nvme-fc: use nr_phys_segments to determine existence of sgl
For some nvme command, when issued by the nvme core layer, there
is an internal buffer which can cause blk_rq_payload_bytes() to
return a non-zero value yet there is no actual/real command payload
and sg list. An example is the WRITE ZEROES command.
To address this, when making choices on whether to dma map an sgl,
use blk_rq_nr_phys_segments() instead of blk_rq_payload_bytes().
When there is a sgl, blk_rq_payload_bytes() will return the amount
of data to be transferred by the sgl.
Signed-off-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Signed-off-by: James Smart <jsmart2021@gmail.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'scripts/package')
0 files changed, 0 insertions, 0 deletions