From: John Garry <john.garry@huawei.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: "axboe@kernel.dk" <axboe@kernel.dk>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kashyap.desai@broadcom.com" <kashyap.desai@broadcom.com>,
"hare@suse.de" <hare@suse.de>
Subject: Re: [PATCH] blk-mq: Fix blk_mq_tagset_busy_iter() for shared tags
Date: Mon, 18 Oct 2021 09:08:57 +0100 [thread overview]
Message-ID: <1065f517-c94b-5a47-34f6-52015b3ef907@huawei.com> (raw)
In-Reply-To: <7e142559-1c96-8d84-081a-378c1f6d1306@huawei.com>
On 13/10/2021 16:13, John Garry wrote:
>> diff --git a/block/blk-mq-tag.c b/block/blk-mq-tag.c
>> index 72a2724a4eee..2a2ad6dfcc33 100644
>> --- a/block/blk-mq-tag.c
>> +++ b/block/blk-mq-tag.c
>> @@ -232,8 +232,9 @@ static bool bt_iter(struct sbitmap *bitmap,
>> unsigned int bitnr, void *data)
>> if (!rq)
>> return true;
>> - if (rq->q == hctx->queue && rq->mq_hctx == hctx)
>> - ret = iter_data->fn(hctx, rq, iter_data->data, reserved);
>> + if (rq->q == hctx->queue && (rq->mq_hctx == hctx ||
>> + blk_mq_is_shared_tags(hctx->flags)))
>> + ret = iter_data->fn(rq->mq_hctx, rq, iter_data->data, reserved);
>> blk_mq_put_rq_ref(rq);
>> return ret;
>> }
>> @@ -460,6 +461,9 @@ void blk_mq_queue_tag_busy_iter(struct
>> request_queue *q, busy_iter_fn *fn,
>> if (tags->nr_reserved_tags)
>> bt_for_each(hctx, &tags->breserved_tags, fn, priv, true);
>> bt_for_each(hctx, &tags->bitmap_tags, fn, priv, false);
>> +
>> + if (blk_mq_is_shared_tags(hctx->flags))
>> + break;
>> }
>> blk_queue_exit(q);
>> }
>>
>
> I suppose that is ok, and means that we iter once.
>
> However, I have to ask, where is the big user of
> blk_mq_queue_tag_busy_iter() coming from? I saw this from Kashyap's mail:
>
> > 1.31% 1.31% kworker/57:1H-k [kernel.vmlinux]
> > native_queued_spin_lock_slowpath
> > ret_from_fork
> > kthread
> > worker_thread
> > process_one_work
> > blk_mq_timeout_work
> > blk_mq_queue_tag_busy_iter
> > bt_iter
> > blk_mq_find_and_get_req
> > _raw_spin_lock_irqsave
> > native_queued_spin_lock_slowpath
>
> How or why blk_mq_timeout_work()?
Just some update: I tried hisi_sas with 10x SAS SSDs, megaraid sas with
1x SATA HDD (that's all I have), and null blk with lots of devices, and
I still can't see high usage of blk_mq_queue_tag_busy_iter().
So how about we get this patch processed (to fix
blk_mq_tagset_busy_iter()), as it is independent of
blk_mq_queue_tag_busy_iter()? And then wait for some update or some more
info from Kashyap regarding blk_mq_queue_tag_busy_iter()
Thanks,
John
next prev parent reply other threads:[~2021-10-18 8:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 8:40 John Garry
2021-10-13 9:22 ` Ming Lei
2021-10-13 10:01 ` John Garry
2021-10-13 10:20 ` Ming Lei
2021-10-13 11:11 ` John Garry
2021-10-13 14:29 ` Ming Lei
2021-10-13 15:13 ` John Garry
2021-10-18 8:08 ` John Garry [this message]
2021-10-18 9:07 ` Ming Lei
2021-10-18 9:33 ` John Garry
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=1065f517-c94b-5a47-34f6-52015b3ef907@huawei.com \
--to=john.garry@huawei.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=kashyap.desai@broadcom.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
/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
all inboxes | Powered by JetHome®