diff options
author | James Smart <jsmart2021@gmail.com> | 2017-09-18 18:08:29 +0200 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2017-09-25 16:56:05 +0200 |
commit | bb1cc74790eb51f52d23c6e5fd9a3bb16030c3d8 (patch) | |
tree | 1590f612ebe76d8a04090d7140d65c3bd84c7346 /fs/direct-io.c | |
parent | nvme-fabrics: Allow 0 as KATO value (diff) | |
download | linux-bb1cc74790eb51f52d23c6e5fd9a3bb16030c3d8.tar.xz linux-bb1cc74790eb51f52d23c6e5fd9a3bb16030c3d8.zip |
nvmet: implement valid sqhd values in completions
To support sqhd, for initiators that are following the spec and
paying attention to sqhd vs their sqtail values:
- add sqhd to struct nvmet_sq
- initialize sqhd to 0 in nvmet_sq_setup
- rather than propagate the 0's-based qsize value from the connect message
which requires a +1 in every sqhd update, and as nothing else references
it, convert to 1's-based value in nvmt_sq/cq_setup() calls.
- validate connect message sqsize being non-zero per spec.
- updated assign sqhd for every completion that goes back.
Also remove handling the NULL sq case in __nvmet_req_complete, as it can't
happen with the current code.
Signed-off-by: James Smart <james.smart@broadcom.com>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Reviewed-by: Max Gurtovoy <maxg@mellanox.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'fs/direct-io.c')
0 files changed, 0 insertions, 0 deletions