From: "Brendan Jackman" <brendan.jackman@linux.dev>
To: "Zi Yan" <ziy@nvidia.com>,
"Brendan Jackman" <brendan.jackman@linux.dev>,
"Brendan Jackman" <jackmanb@google.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Vlastimil Babka" <vbabka@kernel.org>,
"Suren Baghdasaryan" <surenb@google.com>,
"Michal Hocko" <mhocko@suse.com>,
"Johannes Weiner" <hannes@cmpxchg.org>
Cc: "Harry Yoo (Oracle)" <harry@kernel.org>,
"Gregory Price" <gourry@gourry.net>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] mm/page_alloc: drop flag-conversion "optimisation"
Date: Fri, 19 Jun 2026 12:34:53 +0000 [thread overview]
Message-ID: <DJD12YR8S99G.1I43PSHB77TA2@linux.dev> (raw)
In-Reply-To: <DJD0X2R79SVW.1XM7FV4REYCHS@nvidia.com>
On Fri Jun 19, 2026 at 12:27 PM UTC, Zi Yan wrote:
> On Fri Jun 19, 2026 at 7:53 AM EDT, Brendan Jackman wrote:
>> On Mon Jun 15, 2026 at 10:59 AM UTC, Brendan Jackman wrote: > On Mon Jun 15, 2026 at 10:54 AM UTC, Brendan Jackman wrote:
>>>
>>>>
>>>> Signed-off-by: Brendan Jackman <jackmanb@google.com>
>>>> ---
>>>> Changes in v2:
>>>> - Updated alloc_flags_nofragment() too.
>>>> - Link to v1: https://lore.kernel.org/r/20260612-gfp-pessimisation-v1-1-936eb04202e7@google.com
>>>
>>> Sigh, maybe one day I'll send a patch without immediately following up
>>> with a "oops, I forgot to ...". But today is not that day.
>>>
>>> Forgot to add these tags from the v1:
>>>
>>> Reviewed-by: Vlastimil Babka (SUSE) <vbabka@kernel.org>
>>> Reviewed-by: Zi Yan <ziy@nvidia.com>
>>> Reviewed-by: Gregory Price <gourry@gourry.net>
>>> Acked-by: Johannes Weiner <hannes@cmpxchg.org>
>>> Acked-by: Harry Yoo (Oracle) <harry@kernel.org>
>>>
>>> Thanks everyone for the prompt reviews.
>>
>> Hi Andrew,
>>
>> This one didn't make it into any of the latest mm-* branches, is
>> anything blocked here?
>
> It is in the quiet period, no patch will be picked up until -rc1 is
> out. If yours is not picked up then, feel free to resend it.
Ah, I thought mm-unstable didn't care about merge windows. It got
updated 2 days ago, but now I realise that's probably just coz Andrew
was updating mm-stable and then rebased onto it?
Thanks for clarifying.
next prev parent reply other threads:[~2026-06-19 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 10:54 [PATCH v2] mm/page_alloc: drop flag-conversion "optimisation" Brendan Jackman
2026-06-15 10:59 ` Brendan Jackman
2026-06-19 11:53 ` Brendan Jackman
2026-06-19 12:27 ` Zi Yan
2026-06-19 12:34 ` Brendan Jackman [this message]
2026-06-19 14:53 ` David Hildenbrand (Arm)
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=DJD12YR8S99G.1I43PSHB77TA2@linux.dev \
--to=brendan.jackman@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=gourry@gourry.net \
--cc=hannes@cmpxchg.org \
--cc=harry@kernel.org \
--cc=jackmanb@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=ziy@nvidia.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