From: zhiguojiang <justinjiang@vivo.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Johannes Weiner <hannes@cmpxchg.org>,
opensource.kernel@vivo.com
Subject: Re: [PATCH v3] mm: ALLOC_HIGHATOMIC flag allocation issue
Date: Wed, 22 Nov 2023 15:10:30 +0800 [thread overview]
Message-ID: <d46f66b3-cb3e-458a-ba98-508389a601ed@vivo.com> (raw)
In-Reply-To: <ZV2dvlKYSDUu6Uit@casper.infradead.org>
在 2023/11/22 14:20, Matthew Wilcox 写道:
> On Wed, Nov 22, 2023 at 09:39:25AM +0800, Zhiguo Jiang wrote:
>> Update base on the latest Linus' tree or Andrew's tree.
>> +++ b/mm/page_alloc.c
>> @@ -2851,9 +2851,9 @@ struct page *__rmqueue_pcplist(struct zone *zone, unsigned int order,
>> int alloced;
>>
>> /*
>> - * If pcplist is empty and alloc_flags is with ALLOC_HIGHATOMIC,
>> - * it should alloc from buddy highatomic migrate freelist firstly
>> - * to ensure quick and successful allocation.
>> + * If pcplist is empty and alloc_flags contains
>> + * ALLOC_HIGHATOMIC, alloc from buddy highatomic
>> + * freelist first.
> No, it's still based on your earlier patch, is it really so hard for
> you to read your patches before you send them?
Sorry, I didn't understand your meaning correctly before. I have updated
base on the latest linux-next tree in patch v4.
Thank you for your patient guidance.
prev parent reply other threads:[~2023-11-22 7:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231122013925.1507-1-justinjiang@vivo.com>
2023-11-22 6:20 ` Matthew Wilcox
2023-11-22 7:10 ` zhiguojiang [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=d46f66b3-cb3e-458a-ba98-508389a601ed@vivo.com \
--to=justinjiang@vivo.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=opensource.kernel@vivo.com \
--cc=willy@infradead.org \
/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