From: Jens Axboe <axboe@kernel.dk>
To: "zhaoyang.huang" <zhaoyang.huang@unisoc.com>,
Mel Gorman <mgorman@techsingularity.net>,
Zhaoyang Huang <huangzhaoyang@gmail.com>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
ke.wang@unisoc.com
Subject: Re: [RFC PATCHv2] block: set bdi congested when no tag available
Date: Thu, 16 Jun 2022 09:27:43 -0600 [thread overview]
Message-ID: <281b7645-5ce3-0339-78d9-bbc737e4c50e@kernel.dk> (raw)
In-Reply-To: <1655382631-3037-1-git-send-email-zhaoyang.huang@unisoc.com>
On 6/16/22 6:30 AM, zhaoyang.huang wrote:
> From: Zhaoyang Huang <zhaoyang.huang@unisoc.com>
>
> In previous version, block layer will set bdi to be congested when
> get_request fail, which may throttle direct_reclaim. Move them back
> under current blk-mq design.
bdi congestion doesn't exist anymore, not sure what this patch is
against?
--
Jens Axboe
next prev parent reply other threads:[~2022-06-16 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 12:30 [RFC PATCHv2] block: set bdi congested when no tag available zhaoyang.huang
2022-06-16 15:27 ` Jens Axboe [this message]
2022-06-17 6:45 ` 答复: " 黄朝阳 (Zhaoyang Huang)
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=281b7645-5ce3-0339-78d9-bbc737e4c50e@kernel.dk \
--to=axboe@kernel.dk \
--cc=huangzhaoyang@gmail.com \
--cc=ke.wang@unisoc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=zhaoyang.huang@unisoc.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