From: Jens Axboe <axboe@fb.com>
To: Omar Sandoval <osandov@osandov.com>
Cc: linux-block@vger.kernel.org, bart.vanassche@sandisk.com,
hch@lst.de, osandov@fb.com, paolo.valente@linaro.org,
hare@suse.com
Subject: Re: [PATCH 4/5] blk-mq-sched: fix starvation for multiple hardware queues and shared tags
Date: Thu, 26 Jan 2017 13:26:31 -0700 [thread overview]
Message-ID: <0d1d511c-41ea-4677-878a-97cff4fe1956@fb.com> (raw)
In-Reply-To: <20170126202500.GD21449@vader.DHCP.thefacebook.com>
On 01/26/2017 01:25 PM, Omar Sandoval wrote:
> On Thu, Jan 26, 2017 at 12:48:17PM -0700, Jens Axboe wrote:
>> If we have both multiple hardware queues and shared tag map between
>> devices, we need to ensure that we propagate the hardware queue
>> restart bit higher up. This is because we can get into a situation
>> where we don't have any IO pending on a hardware queue, yet we fail
>> getting a tag to start new IO. If that happens, it's not enough to
>> mark the hardware queue as needing a restart, we need to bubble
>> that up to the higher level queue as well.
>
> One minor nit below. Otherwise, makes sense.
>
> Reviewed-by: Omar Sandoval <osandov@fb.com>
>
>> Signed-off-by: Jens Axboe <axboe@fb.com>
>> ---
>> block/blk-mq-sched.c | 28 ++++++++++++++++++++++++++++
>> block/blk-mq-sched.h | 15 +++++++++------
>> block/blk-mq.c | 3 ++-
>> block/blk-mq.h | 1 +
>> include/linux/blkdev.h | 1 +
>> 5 files changed, 41 insertions(+), 7 deletions(-)
>
>> diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
>> index 25564857f5f8..73bcd201a9b7 100644
>> --- a/include/linux/blkdev.h
>> +++ b/include/linux/blkdev.h
>> @@ -602,6 +602,7 @@ struct request_queue {
>> #define QUEUE_FLAG_FLUSH_NQ 25 /* flush not queueuable */
>> #define QUEUE_FLAG_DAX 26 /* device supports DAX */
>> #define QUEUE_FLAG_STATS 27 /* track rq completion times */
>> +#define QUEUE_FLAG_RESTART 28
>
> All of the other queue flags have a comment, could you add one here,
> too?
Definitely, I'll add an appropriate comment.
--
Jens Axboe
next prev parent reply other threads:[~2017-01-26 20:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 19:48 [PATCH 0/5] blk-mq: various blk-mq/blk-mq-sched fixes Jens Axboe
2017-01-26 19:48 ` [PATCH 1/5] blk-mq: improve scheduler queue sync/async running Jens Axboe
2017-01-26 19:59 ` Omar Sandoval
2017-01-26 19:48 ` [PATCH 2/5] blk-mq: fix potential race in queue restart and driver tag allocation Jens Axboe
2017-01-26 19:52 ` Jens Axboe
2017-01-26 20:04 ` Omar Sandoval
2017-01-26 19:48 ` [PATCH 3/5] blk-mq: release driver tag on a requeue event Jens Axboe
2017-01-26 20:06 ` Omar Sandoval
2017-01-26 19:48 ` [PATCH 4/5] blk-mq-sched: fix starvation for multiple hardware queues and shared tags Jens Axboe
2017-01-26 20:25 ` Omar Sandoval
2017-01-26 20:26 ` Jens Axboe [this message]
2017-01-26 19:48 ` [PATCH 5/5] blk-mq-sched: change ->dispatch_requests() to ->dispatch_request() Jens Axboe
2017-01-26 20:54 ` Omar Sandoval
2017-01-26 20:59 ` Jens Axboe
2017-01-26 21:11 ` Omar Sandoval
2017-01-26 21:15 ` Jens Axboe
2017-01-27 12:10 ` [PATCH 0/5] blk-mq: various blk-mq/blk-mq-sched fixes Hannes Reinecke
2017-01-27 14:40 ` 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=0d1d511c-41ea-4677-878a-97cff4fe1956@fb.com \
--to=axboe@fb.com \
--cc=bart.vanassche@sandisk.com \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=osandov@fb.com \
--cc=osandov@osandov.com \
--cc=paolo.valente@linaro.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