blk-mq: Avoid effects of a weird queue depth
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | blk-mq: Sanity check reserved tagsblock/ | +2 | 0 replies | |
| 2/3 | blk-mq: Check queue depth is validblock/ block/ block/ | +17 | 0 replies | |
| 3/3 | blk-mq: Do not allocate more cache entries than usedblock/ | +16 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] blk-mq: Avoid effects of a weird queue depth
Hi Jens,
This series aimed to avoid effects of a weird queue depth, i.e when less than reserved_tags requested or insufficient number of requests were allocated.
In case number of normal (not reserved) tags is requested less than 4 (current minimal cache size limit) there are two options to resolve: adjust cache size to the depth or deny queue depths less than the minimal cache size. I favored the latter, but will repost if you prefer otherwise.
Alexander Gordeev (3):
blk-mq: Sanity check reserved tags
blk-mq: Check queue depth is valid
blk-mq: Do not allocate more cache entries than used
block/blk-mq-tag.c | 31 ++++++++++++++++++------------- block/blk-mq-tag.h | 6 ++++++ block/blk-mq.c | 12 +++++++----- 3 files changed, 31 insertions(+), 18 deletions(-)
Signature · 7 lines
1.7.7.6 -- Regards, Alexander Gordeev [email protected]