From: Qianfeng Rong <rongqianfeng@vivo.com>
To: Yu Kuai <yukuai1@huaweicloud.com>, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH] block, bfq: remove redundant __GFP_NOWARN
Date: Mon, 11 Aug 2025 15:40:32 +0800 [thread overview]
Message-ID: <6bf7177d-ceac-40b4-8f79-e211ecaa42b1@vivo.com> (raw)
In-Reply-To: <233497ad-4d0e-2aa0-96ab-fbabdc68bb5e@huaweicloud.com>
在 2025/8/11 8:59, Yu Kuai 写道:
> [You don't often get email from yukuai1@huaweicloud.com. Learn why
> this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> Hi,
>
> 在 2025/08/09 22:22, Qianfeng Rong 写道:
>> Commit 16f5dfbc851b ("gfp: include __GFP_NOWARN in GFP_NOWAIT") made
>> GFP_NOWAIT implicitly include __GFP_NOWARN.
>>
>> Therefore, explicit __GFP_NOWARN combined with GFP_NOWAIT (e.g.,
>> `GFP_NOWAIT | __GFP_NOWARN`) is now redundant. Let's clean up these
>> redundant flags across subsystems.
>>
>> Signed-off-by: Qianfeng Rong <rongqianfeng@vivo.com>
>> ---
>> block/bfq-iosched.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/block/bfq-iosched.c b/block/bfq-iosched.c
>> index 3bf76902f07f..db0ae65186ec 100644
>> --- a/block/bfq-iosched.c
>> +++ b/block/bfq-iosched.c
>> @@ -5848,7 +5848,7 @@ static struct bfq_queue *bfq_get_queue(struct
>> bfq_data *bfqd,
>> }
>>
>> bfqq = kmem_cache_alloc_node(bfq_pool,
>> - GFP_NOWAIT | __GFP_ZERO |
>> __GFP_NOWARN,
>> + GFP_NOWAIT | __GFP_ZERO,
> Can you also combine this line with the one above?
OK, I'll post the second version soon.
Best regards,
Qianfeng
>
> Otherwise LGTM. Feel free to add:
>
> Reviewed-by: Yu Kuai <yukuai3@huawei.com>
>
>> bfqd->queue->node);
>>
>> if (bfqq) {
>>
>
prev parent reply other threads:[~2025-08-11 7:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-09 14:22 Qianfeng Rong
2025-08-11 0:59 ` Yu Kuai
2025-08-11 7:40 ` Qianfeng Rong [this message]
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=6bf7177d-ceac-40b4-8f79-e211ecaa42b1@vivo.com \
--to=rongqianfeng@vivo.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.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®