From: Rik van Riel <riel@surriel.com>
To: Dev Jain <dev.jain@arm.com>, linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, ryan.roberts@arm.com,
akpm@linux-foundation.org, david@kernel.org, ljs@kernel.org,
liam@infradead.org, vbabka@kernel.org, rppt@kernel.org,
surenb@google.com, mhocko@suse.com, kasong@tencent.com,
qi.zheng@linux.dev, shakeel.butt@linux.dev, hannes@cmpxchg.org,
brendan.jackman@linux.dev, ziy@nvidia.com
Subject: Re: [RFC NO CODE] [DISCUSSION] Anti-fragmenting ordered buddy allocator
Date: Sun, 11 Oct 2026 17:59:38 -0400 [thread overview]
Message-ID: <16a9c5ef3fde0b7693e52dac91a2d397526dd99b.camel@surriel.com> (raw)
In-Reply-To: <20261011215412.1181172-1-dev.jain@arm.com>
On Sun, 2026-10-11 at 21:54 +0000, Dev Jain wrote:
>
>
> Apart from dividing the freelists between migratetypes, little
> attempt
> has been made to change the algorithm
Could I convince you to take a look at these
patches?
https://lore.kernel.org/all/20261007021250.1665929-1-riel@surriel.com/
My current plan is to first improve the
fragmentation at pageblock level, and then
add some slow path code on top of that
which can steer the allocations by physical
address range, to preserve the potential
for gigablock page lalocation.
--
All Rights Reversed.
next prev parent reply other threads:[~2026-10-11 22:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 21:54 Dev Jain
2026-10-11 21:59 ` Rik van Riel [this message]
2026-10-12 10:13 ` Dev Jain
2026-10-11 23:04 ` Zi Yan
2026-10-12 10:10 ` Dev Jain
2026-10-12 8:25 ` Pedro Falcato
2026-10-12 10:34 ` Dev Jain
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=16a9c5ef3fde0b7693e52dac91a2d397526dd99b.camel@surriel.com \
--to=riel@surriel.com \
--cc=akpm@linux-foundation.org \
--cc=brendan.jackman@linux.dev \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--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=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--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®