From: Dev Jain <dev.jain@arm.com>
To: Rik van Riel <riel@surriel.com>, linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Kairui Song <kasong@tencent.com>,
Qi Zheng <qi.zheng@linux.dev>,
Shakeel Butt <shakeel.butt@linux.dev>,
Johannes Weiner <hannes@cmpxchg.org>,
Brendan Jackman <brendan.jackman@linux.dev>,
Zi Yan <ziy@nvidia.com>
Subject: Re: [RFC PROTOTYPE] mm: reliable 1GB page allocation
Date: Mon, 12 Oct 2026 11:08:24 +0530 [thread overview]
Message-ID: <e2152674-e0af-4b07-9115-4668917171b1@arm.com> (raw)
In-Reply-To: <003fdeb213ca0460c8681d4ae7baa562b337ed1a.camel@surriel.com>
On 12/10/26 3:14 am, Rik van Riel wrote:
> On Sun, 2026-10-11 at 22:58 +0530, Dev Jain wrote:
>>
>>
>> On 04/10/26 11:06 am, Rik van Riel wrote:
>>>
>>> When the kernel free lists run low, the slow path moves pages and
>>> page
>>> blocks from inside mixed gigablocks onto the kernel free lists.
>>
>> Did you consider a design to introduce MIGRATE_POLLUTED: simply
>> have another migratetype which stores polluted pageblocks.
>> This idea can work in general, not sure how relevant it is
>> for gigablock concept.
>>
> Don't the first half a dozen or so changes from this
> prototype do that already?
>
> What differences do you have in mind?
Sorry, it was just a drive-by comment. I will eventually try to
review your design document.
>
>
prev parent reply other threads:[~2026-10-12 5:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 5:36 Rik van Riel
2026-10-11 17:28 ` Dev Jain
2026-10-11 21:44 ` Rik van Riel
2026-10-12 5:38 ` Dev Jain [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=e2152674-e0af-4b07-9115-4668917171b1@arm.com \
--to=dev.jain@arm.com \
--cc=akpm@linux-foundation.org \
--cc=brendan.jackman@linux.dev \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kasong@tencent.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=qi.zheng@linux.dev \
--cc=riel@surriel.com \
--cc=rppt@kernel.org \
--cc=shakeel.butt@linux.dev \
--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
all inboxes | Powered by JetHome®