From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Vlastimil Babka <vbabka@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Thadeu Lima de Souza Cascardo <cascardo@igalia.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
Brendan Jackman <jackmanb@google.com>,
Johannes Weiner <hannes@cmpxchg.org>, Zi Yan <ziy@nvidia.com>,
Mel Gorman <mgorman@techsingularity.net>,
kernel-dev@igalia.com, Helen Koike <koike@igalia.com>,
Matthew Wilcox <willy@infradead.org>,
Thierry Reding <thierry.reding@gmail.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
neil@brown.name
Subject: Re: [PATCH] mm/page_alloc: only set ALLOC_HIGHATOMIC for __GPF_HIGH allocations
Date: Fri, 29 Aug 2025 17:56:37 +0900 [thread overview]
Message-ID: <filznxw2rq5ylpawl3auho7luiyaqxkmitf76bbpxyihkbkw43@pos7qfwb3i56> (raw)
In-Reply-To: <77058118-b481-4c45-8f86-d9a67ea6a187@suse.cz>
On (25/08/29 10:38), Vlastimil Babka wrote:
> On 8/29/25 10:36, Vlastimil Babka wrote:
> > On 8/14/25 19:22, Thadeu Lima de Souza Cascardo wrote:
[..]
> > Agreed with others that this change matches the original intention and it
> > must have been an oversight. Also found nothing to the contrary in the
> > original threads.
>
> Oops, forgot to add
>
> Reviewed-by: Vlastimil Babka <vbabka@suse.cz>
Thank you!
FWIW
Tested-by: Sergey Senozhatsky <senozhatsky@chromium.org>
This needs Cc: stable@vger.kernel.org all the way down to 5.15,
as far as I can tell.
next prev parent reply other threads:[~2025-08-29 8:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 17:22 Thadeu Lima de Souza Cascardo
2025-08-14 20:12 ` Johannes Weiner
2025-08-14 20:34 ` Thadeu Lima de Souza Cascardo
2025-08-28 5:06 ` Sergey Senozhatsky
2025-08-29 6:41 ` Michal Hocko
2025-08-29 8:36 ` Vlastimil Babka
2025-08-29 8:38 ` Vlastimil Babka
2025-08-29 8:56 ` Sergey Senozhatsky [this message]
2025-08-29 9:30 ` Vlastimil Babka
2025-08-29 10:30 ` Thadeu Lima de Souza Cascardo
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=filznxw2rq5ylpawl3auho7luiyaqxkmitf76bbpxyihkbkw43@pos7qfwb3i56 \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=cascardo@igalia.com \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=kernel-dev@igalia.com \
--cc=koike@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=neil@brown.name \
--cc=surenb@google.com \
--cc=thierry.reding@gmail.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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