From: Andrew Morton <akpm@linux-foundation.org>
To: "zhaoyang.huang" <zhaoyang.huang@unisoc.com>
Cc: Vlastimil Babka <vbabka@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Brendan Jackman <jackmanb@google.com>, Zi Yan <ziy@nvidia.com>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
Zhaoyang Huang <huangzhaoyang@gmail.com>, <steve.kang@unisoc.com>
Subject: Re: [PATCH] mm: free HIGHATOMIC and CMA frozen pages via buddy
Date: Mon, 25 May 2026 13:15:01 -0700 [thread overview]
Message-ID: <20260525131501.f232fd3cfb67442d2c284631@linux-foundation.org> (raw)
In-Reply-To: <20260525071033.1104929-1-zhaoyang.huang@unisoc.com>
On Mon, 25 May 2026 15:10:33 +0800 "zhaoyang.huang" <zhaoyang.huang@unisoc.com> wrote:
> Pages in pageblocks above MIGRATE_PCPTYPES were remapped to
> MIGRATE_MOVABLE on the per-CPU lists, so order-9 GFP_ATOMIC
> allocations could consume CMA physical blocks which may lead to
> cma_alloc failed.
> This commit would like to free them through free_one_page() simply.
Can you please describe the userspace-visible effects of this change?
Before and after. And include this description within the patch
changelog.
AI review claims to have found a couple of issues, one of which sounds
serious:
https://sashiko.dev/#/patchset/20260525071033.1104929-1-zhaoyang.huang@unisoc.com
Thanks.
next prev parent reply other threads:[~2026-05-25 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 7:10 zhaoyang.huang
2026-05-25 20:15 ` Andrew Morton [this message]
2026-05-26 1:02 ` Zhaoyang Huang
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=20260525131501.f232fd3cfb67442d2c284631@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=huangzhaoyang@gmail.com \
--cc=jackmanb@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=steve.kang@unisoc.com \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=zhaoyang.huang@unisoc.com \
--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
all inboxes | Powered by JetHome®