From: Alexander Gordeev <agordeev@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
Mike Christie <michaelc@cs.wisc.edu>,
Shaohua Li <shli@fusionio.com>
Subject: [PATCH 0/3] blk-mq: Avoid effects of a weird queue depth
Date: Fri, 2 Aug 2013 16:04:55 +0200 [thread overview]
Message-ID: <cover.1375451955.git.agordeev@redhat.com> (raw)
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(-)
--
1.7.7.6
--
Regards,
Alexander Gordeev
agordeev@redhat.com
next reply other threads:[~2013-08-02 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 14:04 Alexander Gordeev [this message]
2013-08-02 14:05 ` [PATCH 1/3] blk-mq: Sanity check reserved tags Alexander Gordeev
2013-08-02 14:05 ` [PATCH 2/3] blk-mq: Check queue depth is valid Alexander Gordeev
2013-08-02 14:06 ` [PATCH 3/3] blk-mq: Do not allocate more cache entries than used Alexander Gordeev
2013-08-21 15:27 ` [PATCH 4/5] blk-mq: Do not fail blk_mq_reg::queue_depth value of zero Alexander Gordeev
2013-08-21 15:28 ` [PATCH 5/5] blk-mq: Lower minimum queue depth from 4 to 1 Alexander Gordeev
2013-09-12 7:42 ` [PATCH 0/3] blk-mq: Avoid effects of a weird queue depth Alexander Gordeev
2013-09-12 14:36 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1375451955.git.agordeev@redhat.com \
--to=agordeev@redhat.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=nab@linux-iscsi.org \
--cc=shli@fusionio.com \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox