diff options
author | James Smart <[email protected]> | 2017-09-18 09:08:29 -0700 |
---|---|---|
committer | Jens Axboe <[email protected]> | 2017-09-25 08:56:05 -0600 |
commit | bb1cc74790eb51f52d23c6e5fd9a3bb16030c3d8 (patch) | |
tree | 1590f612ebe76d8a04090d7140d65c3bd84c7346 /tools/perf/scripts/python/stackcollapse.py | |
parent | 8edd11c9ad3a6205eea6de9d02eaf64c681a0658 (diff) |
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 <[email protected]>
Reviewed-by: Sagi Grimberg <[email protected]>
Reviewed-by: Max Gurtovoy <[email protected]>
Signed-off-by: Christoph Hellwig <[email protected]>
Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions