From: Ming Lei <ming.lei@redhat.com>
To: ZhangHui <zhanghui31@xiaomi.com>
Cc: axboe@kernel.dk, bvanassche@acm.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, ming.lei@redhat.com
Subject: Re: [PATCH v3] block: move non sync requests complete flow to softirq
Date: Wed, 4 Sep 2024 16:01:36 +0800 [thread overview]
Message-ID: <ZtgT4HhEsyRJMoQH@fedora> (raw)
In-Reply-To: <20240903115437.42307-1-zhanghui31@xiaomi.com>
On Tue, Sep 03, 2024 at 07:54:37PM +0800, ZhangHui wrote:
> From: zhanghui <zhanghui31@xiaomi.com>
>
> Currently, for a controller that supports multiple queues, like UFS4.0,
> the mq_ops->complete is executed in the interrupt top-half. Therefore,
> the file system's end io is executed during the request completion process,
> such as f2fs_write_end_io on smartphone.
>
> However, we found that the execution time of the file system end io
> is strongly related to the size of the bio and the processing speed
> of the CPU. Because the file system's end io will traverse every page
> in bio, this is a very time-consuming operation.
>
> We measured that the 80M bio write operation on the little CPU will
What is 80M bio?
It is one known issue that soft lockup may be triggered in case of N:M
blk-mq mapping, but not sure if that is the case.
What is nr_hw_queues(blk_mq) and nr_cpus in your system?
> cause the execution time of the top-half to be greater than 100ms.
> The CPU tick on a smartphone is only 4ms, which will undoubtedly affect
> scheduling efficiency.
schedule is off too in softirq(bottom-half).
>
> Let's fixed this issue by moved non sync request completion flow to
> softirq, and keep the sync request completion in the top-half.
If you do care interrupt-off or schedule-off latency, you may have to move
the IO handling into thread context in the driver.
BTW, threaded irq can't help you too.
Thanks,
Ming
next prev parent reply other threads:[~2024-09-04 8:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 11:54 [PATCH v3] block: move non sync requests complete flow to softirq ZhangHui
2024-09-03 17:28 ` Bart Van Assche
2024-09-03 17:47 ` Jens Axboe
2024-09-04 3:35 ` [External Mail]Re: " 章辉
2024-09-04 17:22 ` Bart Van Assche
2024-09-05 3:05 ` 章辉
2024-09-03 17:49 ` Jens Axboe
2024-09-04 3:25 ` [External Mail]Re: " 章辉
2024-09-04 4:29 ` Christoph Hellwig
2024-09-05 2:52 ` [External Mail]Re: " 章辉
2024-09-04 8:01 ` Ming Lei [this message]
2024-09-05 2:46 ` 章辉
2024-09-05 3:49 ` Ming Lei
2024-09-05 7:33 ` 章辉
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=ZtgT4HhEsyRJMoQH@fedora \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhanghui31@xiaomi.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;
as well as URLs for NNTP newsgroup(s).