From: Muchun Song <muchun.song@linux.dev>
To: Jens Axboe <axboe@kernel.dk>
Cc: Muchun Song <songmuchun@bytedance.com>,
Ming Lei <ming.lei@redhat.com>, Yu Kuai <yukuai1@huaweicloud.com>,
"open list:BLOCK LAYER" <linux-block@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH v2 1/3] block: fix missing dispatching request when queue is started or unquiesced
Date: Wed, 11 Sep 2024 10:43:56 +0800 [thread overview]
Message-ID: <476C2322-BD02-4631-9588-E182847F9EC6@linux.dev> (raw)
In-Reply-To: <0e4e1f5a-30fd-430b-99ec-8b1004d8e3fd@kernel.dk>
> On Sep 10, 2024, at 21:17, Jens Axboe <axboe@kernel.dk> wrote:
>
> On 9/3/24 2:16 AM, Muchun Song wrote:
>> Supposing the following scenario with a virtio_blk driver.
>>
>> CPU0 CPU1 CPU2
>>
>> blk_mq_try_issue_directly()
>> __blk_mq_issue_directly()
>> q->mq_ops->queue_rq()
>> virtio_queue_rq()
>> blk_mq_stop_hw_queue()
>> blk_mq_try_issue_directly() virtblk_done()
>> if (blk_mq_hctx_stopped())
>> blk_mq_request_bypass_insert() blk_mq_start_stopped_hw_queue()
>> blk_mq_run_hw_queue() blk_mq_run_hw_queue()
>> blk_mq_insert_request()
>> return // Who is responsible for dispatching this IO request?
>>
>> After CPU0 has marked the queue as stopped, CPU1 will see the queue is stopped.
>> But before CPU1 puts the request on the dispatch list, CPU2 receives the interrupt
>> of completion of request, so it will run the hardware queue and marks the queue
>> as non-stopped. Meanwhile, CPU1 also runs the same hardware queue. After both CPU1
>> and CPU2 complete blk_mq_run_hw_queue(), CPU1 just puts the request to the same
>> hardware queue and returns. It misses dispatching a request. Fix it by running
>> the hardware queue explicitly. And blk_mq_request_issue_directly() should handle
>> a similar situation. Fix it as well.
>
> Patch looks fine, but this commit message is waaaaay too wide. Please
> limit it to 72-74 chars. The above ordering is diagram is going to
> otherwise be unreadable in a git log viewing in a terminal.
Thanks for your reply. I'll adjust those lines to make the digram more
readable.
Muchun,
Thanks.
>
> --
> Jens Axboe
next prev parent reply other threads:[~2024-09-11 2:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 8:16 [PATCH v2 0/3] Fix some starvation problems in block layer Muchun Song
2024-09-03 8:16 ` [PATCH v2 1/3] block: fix missing dispatching request when queue is started or unquiesced Muchun Song
2024-09-10 13:17 ` Jens Axboe
2024-09-11 2:43 ` Muchun Song [this message]
2024-09-03 8:16 ` [PATCH v2 2/3] block: fix ordering between checking QUEUE_FLAG_QUIESCED and adding requests Muchun Song
2024-09-04 12:56 ` Ming Lei
2024-09-10 13:22 ` Jens Axboe
2024-09-11 3:54 ` Ming Lei
2024-09-11 3:59 ` Muchun Song
2024-09-11 5:20 ` Muchun Song
2024-09-12 3:27 ` Muchun Song
2024-09-12 6:27 ` Muchun Song
2024-09-11 3:56 ` Muchun Song
2024-09-03 8:16 ` [PATCH v2 3/3] block: fix ordering between checking BLK_MQ_S_STOPPED " Muchun Song
2024-09-04 13:04 ` Ming Lei
2024-09-10 13:22 ` Jens Axboe
2024-09-11 2:44 ` Muchun Song
2024-09-10 2:49 ` [PATCH v2 0/3] Fix some starvation problems in block layer Muchun Song
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=476C2322-BD02-4631-9588-E182847F9EC6@linux.dev \
--to=muchun.song@linux.dev \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=songmuchun@bytedance.com \
--cc=stable@vger.kernel.org \
--cc=yukuai1@huaweicloud.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.