* Re: [PATCH v3] mm: ALLOC_HIGHATOMIC flag allocation issue
[not found] <20231122013925.1507-1-justinjiang@vivo.com>
@ 2023-11-22 6:20 ` Matthew Wilcox
2023-11-22 7:10 ` zhiguojiang
0 siblings, 1 reply; 2+ messages in thread
From: Matthew Wilcox @ 2023-11-22 6:20 UTC (permalink / raw)
To: Zhiguo Jiang
Cc: Andrew Morton, linux-mm, linux-kernel, Johannes Weiner,
opensource.kernel
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?
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH v3] mm: ALLOC_HIGHATOMIC flag allocation issue
2023-11-22 6:20 ` [PATCH v3] mm: ALLOC_HIGHATOMIC flag allocation issue Matthew Wilcox
@ 2023-11-22 7:10 ` zhiguojiang
0 siblings, 0 replies; 2+ messages in thread
From: zhiguojiang @ 2023-11-22 7:10 UTC (permalink / raw)
To: Matthew Wilcox
Cc: Andrew Morton, linux-mm, linux-kernel, Johannes Weiner,
opensource.kernel
在 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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-11-22 7:10 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20231122013925.1507-1-justinjiang@vivo.com>
2023-11-22 6:20 ` [PATCH v3] mm: ALLOC_HIGHATOMIC flag allocation issue Matthew Wilcox
2023-11-22 7:10 ` zhiguojiang
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox