From: Ming Lei <ming.lei@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Subject: Re: [PATCH 2/2] blk-mq: Improve performance of non-mq IO schedulers with multiple HW queues
Date: Thu, 7 Jan 2021 20:06:47 +0800 [thread overview]
Message-ID: <20210107120647.GA3915822@T590> (raw)
In-Reply-To: <20210107111815.GB12990@quack2.suse.cz>
On Thu, Jan 07, 2021 at 12:18:15PM +0100, Jan Kara wrote:
> On Thu 07-01-21 14:19:18, Ming Lei wrote:
> > On Wed, Jan 06, 2021 at 11:24:28AM +0100, Jan Kara wrote:
> > > +/* Check if there are requests queued in hctx lists. */
> > > +static bool blk_mq_hctx_has_queued_rq(struct blk_mq_hw_ctx *hctx)
> > > +{
> > > + return !list_empty_careful(&hctx->dispatch) ||
> > > + sbitmap_any_bit_set(&hctx->ctx_map);
> > > +}
> > > +
> >
> > blk_mq_hctx_mark_pending() is only called in case of none scheduler, so
> > looks not necessary to check hctx->ctx_map in blk_mq_hctx_has_queued_rq()
> > which is supposed to be used when real io scheduler is attached to MQ queue.
>
> Yes, I know. I just wanted to make the code less fragile... In particular I
> was somewhat uneasy that we'd rely on the implicit behavior that
> blk_mq_get_sqsched_hctx() can return non-NULL only if sbitmap_any_bit_set()
> is not needed. But maybe we could structure the code like:
BTW, I mentioned the point because sbitmap_any_bit_set(hctx->ctx_map) may take
some CPU cycle in case that nr_cpu_ids is big.
>
> sq_hctx = NULL;
> if (blk_mq_has_sqsched(q))
> sq_hctx = blk_mq_get_sq_hctx(q);
> queue_for_each_hw_ctx(q, hctx, i) {
> ...
> if (!sq_hctx || sq_hctx == hctx ||
> !list_empty_careful(&hctx->dispatch))
> ... run ...
> }
>
> Because then it is kind of obvious that sq_hctx is set only if there's IO
> scheduler for the queue and thus ctx_map is unused. What do you think?
IMO, the above is more readable and efficient.
Thanks,
Ming
next prev parent reply other threads:[~2021-01-07 12:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 10:24 [PATCH 0/2 v2] blk-mq: Improve performance of non-mq IO schedulers with multiple HW queues Jan Kara
2021-01-06 10:24 ` [PATCH 1/2] Revert "blk-mq, elevator: Count requests per hctx to improve performance" Jan Kara
2021-01-06 10:24 ` [PATCH 2/2] blk-mq: Improve performance of non-mq IO schedulers with multiple HW queues Jan Kara
2021-01-07 6:19 ` Ming Lei
2021-01-07 11:18 ` Jan Kara
2021-01-07 12:06 ` Ming Lei [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-11 16:47 [PATCH 0/2 v3] " Jan Kara
2021-01-11 16:47 ` [PATCH 2/2] " Jan Kara
2021-01-12 2:15 ` Ming Lei
2020-12-18 21:44 [PATCH 0/2 RFC] " Jan Kara
2020-12-18 21:44 ` [PATCH 2/2] " Jan Kara
2020-12-19 3:14 ` Ming Lei
2020-12-22 10:18 ` Jan Kara
2020-12-22 16:55 ` Jan Kara
2020-12-23 3:43 ` Ming Lei
2020-12-23 3:33 ` Ming Lei
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=20210107120647.GA3915822@T590 \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=jack@suse.cz \
--cc=linux-block@vger.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;
as well as URLs for NNTP newsgroup(s).