From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Juan Yescas <jyescas@google.com>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
open list <linux-kernel@vger.kernel.org>,
"open list:MEMORY MANAGEMENT - CORE" <linux-mm@kvack.org>,
android-mm@google.com, fvdl@google.com, tkjos@google.com,
minchan@google.com, dskiba@google.com
Subject: Re: [RFC PATCH 00/16] Page Alloc Hogger
Date: Fri, 31 Jul 2026 16:55:05 +0100 [thread overview]
Message-ID: <amzAPXR_rBqj7qr9@lucifer> (raw)
In-Reply-To: <CAJDx_rih=0qWpfsnOQYbEwgG1OgPEK23MacTUsJndjiNLV+CGg@mail.gmail.com>
On Fri, Jul 31, 2026 at 08:32:35AM -0700, Juan Yescas wrote:
> On Thu, Jul 30, 2026 at 12:51 AM Lorenzo Stoakes (ARM) <ljs@kernel.org> wrote:
> >
> > On Tue, Jul 28, 2026 at 05:36:03PM -0700, Juan Yescas wrote:
> > > On Tue, Jul 28, 2026 at 12:29 PM David Hildenbrand (Arm)
> > > <david@kernel.org> wrote:
> > > >
> > > > On 7/23/26 09:47, Juan Yescas wrote:
> > > > > This patch series introduces the Page Alloc Hogger. The Page Alloc Hogger
> > > > > allows you to allocate memory pages from specific nodes, zones, migration
> > > > > types, and orders directly via debugfs. This provides key benefits for
> > > > > testing and debugging:
> > > >
> > > > Would it be feasible to carry this as an OOT debugging module? Would a lot of
> > > > symbols be missing to achieve that?
> > > >
> > >
> > > Thanks David for the comment.
> > >
> > > The only symbol that would be needed to have this module as OOT is
> > > "migratetype_names".
> >
> > I mean you could hardcode these and be pretty safe :) I don't we're going
> > to add any time soon and if we did you'd probably need to change the module
> > code anyway?
>
> Thanks Lorenzo, I agree, the names can be hardcoded.
Yeah :) I think not such an issue.
>
> > I feel this debug module should be a noop in core.
>
> What would be the main concern here?
>
> The reason I wrote this module is because my team and system teams who
> work in memory,
> have programs to alloc/free memory to debug memory issues. These
> programs are not shared and
> depending on the memory issue, developers customize their programs. If we want
> to allocate memory that is not MOVABLE, we need to write custom kernel
> drivers for that. This code
> is reinvented constantly by developers.
Exposing internal implementation details via debugfs is problematic as a core
feature.
It's not impossible for this to be upstream however as a separate driver on the
basis of people re-inventing?
>
> With this self contained module, we can allocate any valid memory from
> any node/zone/order/migrate type
> without needing custom programs or drivers.
>
> Greetings
> Juan
>
> > Cheers, Lorenzo
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-07-31 15:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 7:47 [RFC PATCH 00/16] Page Alloc Hogger Juan Yescas
2026-07-23 7:47 ` [RFC PATCH 01/16] mm: Page Alloc Hogger module Juan Yescas
2026-07-23 7:47 ` [RFC PATCH 02/16] mm: Define structs for allocation requests and store allocations Juan Yescas
2026-07-23 7:47 ` [RFC PATCH 03/16] mm: Define the caches for the structs req_alloc and page_alloc Juan Yescas
2026-07-23 7:47 ` [RFC PATCH 04/16] mm: Define function to create a dir for each online node Juan Yescas
2026-07-23 7:47 ` [RFC PATCH 05/16] mm: Define function to create a dir for populated zone Juan Yescas
2026-07-23 7:47 ` [RFC PATCH 06/16] mm: Define function to create a dir for each page order Juan Yescas
2026-07-23 7:47 ` [RFC PATCH 07/16] mm: Define function to create a dir for each migrate type Juan Yescas
2026-07-23 7:47 ` [RFC PATCH 08/16] mm: Define function that creates the "nr_pages_allocs" file Juan Yescas
2026-07-23 7:47 ` [RFC PATCH 09/16] mm: Read the nr_pages_allocs value given by user Juan Yescas
2026-07-23 7:47 ` [RFC PATCH 10/16] mm: Set the selected zone in gfp_t flags Juan Yescas
2026-07-23 7:47 ` [RFC PATCH 11/16] mm: Sets the migrate type " Juan Yescas
2026-07-23 7:47 ` [RFC PATCH 12/16] mm: Define the make_alloc() function Juan Yescas
2026-07-23 7:47 ` [RFC PATCH 13/16] mm: Create the file asociated with an allocation Juan Yescas
2026-07-23 7:47 ` [RFC PATCH 14/16] mm: Free pages, remove files and clean cache when one alloc fails Juan Yescas
2026-07-23 7:47 ` [RFC PATCH 15/16] mm: Create the "free" file to release the previously allocated pages Juan Yescas
2026-07-23 7:47 ` [RFC PATCH 16/16] mm: Release resources when the page alloc hogger module exits Juan Yescas
2026-07-28 19:29 ` [RFC PATCH 00/16] Page Alloc Hogger David Hildenbrand (Arm)
2026-07-29 0:36 ` Juan Yescas
2026-07-30 7:50 ` Lorenzo Stoakes (ARM)
2026-07-31 15:32 ` Juan Yescas
2026-07-31 15:55 ` Lorenzo Stoakes (ARM) [this message]
2026-07-31 12:40 ` Lorenzo Stoakes (ARM)
2026-07-31 12:42 ` Lorenzo Stoakes (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=amzAPXR_rBqj7qr9@lucifer \
--to=ljs@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=android-mm@google.com \
--cc=david@kernel.org \
--cc=dskiba@google.com \
--cc=fvdl@google.com \
--cc=jyescas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=minchan@google.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=tkjos@google.com \
--cc=vbabka@suse.cz \
/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