Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Juan Yescas <jyescas@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	 David Hildenbrand <david@kernel.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 v2 00/16] Page Alloc Hogger
Date: Thu, 6 Aug 2026 10:48:39 +0100	[thread overview]
Message-ID: <anRRLwa3N5bVCHET@lucifer> (raw)
In-Reply-To: <20260806011048.517229-1-jyescas@google.com>

Hi Juan,

While I think there's possibly value in people not re-implemented their own
allocation injector, I don't think there's value in having this be part of
core-mm.

I really don't want this to form part of any contract or to be blessed in
any way by core mm as it exposes internal implementation details and I
really want to avoid adding extra maintainer workload here.

I'd suggest keeping it as an out-of-tree module as David proposed
previously ([0]).

Alternatively, keeping it as part of tooling (e.g. in tools/testing) could
also work.

(This is no comment on how useful it might be for debugging or testing
scenarios :)

--
Cheers, Lorenzo

[0]:https://lore.kernel.org/all/97605949-82c5-49e0-84b6-b42e8078b55d@kernel.org/


  parent reply	other threads:[~2026-08-06  9:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06  1:09 [RFC PATCH v2 00/16] Page Alloc Hogger Juan Yescas
2026-08-06  1:09 ` [RFC PATCH v2 01/16] mm: Page Alloc Hogger module Juan Yescas
2026-08-06  1:09 ` [RFC PATCH v2 02/16] mm: Define structs for allocation requests and store allocations Juan Yescas
2026-08-06  1:09 ` [RFC PATCH v2 03/16] mm: Define the caches for the structs req_alloc and page_alloc Juan Yescas
2026-08-06  1:09 ` [RFC PATCH v2 04/16] mm: Define function to create a dir for each online node Juan Yescas
2026-08-06  1:09 ` [RFC PATCH v2 05/16] mm: Define function to create a dir for populated zone Juan Yescas
2026-08-06  1:09 ` [RFC PATCH v2 06/16] mm: Define function to create a dir for each page order Juan Yescas
2026-08-06  1:09 ` [RFC PATCH v2 07/16] mm: Define function to create a dir for each migrate type Juan Yescas
2026-08-06  1:09 ` [RFC PATCH v2 08/16] mm: Define function that creates the "nr_pages_allocs" file Juan Yescas
2026-08-06  1:09 ` [RFC PATCH v2 09/16] mm: Read the nr_pages_allocs value given by user Juan Yescas
2026-08-06  1:09 ` [RFC PATCH v2 10/16] mm: Set the selected zone in gfp_t flags Juan Yescas
2026-08-06  1:09 ` [RFC PATCH v2 11/16] mm: Sets the migrate type " Juan Yescas
2026-08-06  1:09 ` [RFC PATCH v2 12/16] mm: Define the make_alloc() function Juan Yescas
2026-08-06  1:09 ` [RFC PATCH v2 13/16] mm: Create the file associated with an allocation Juan Yescas
2026-08-06  1:09 ` [RFC PATCH v2 14/16] mm: Free pages, remove files and clean cache when one alloc fails Juan Yescas
2026-08-06  1:09 ` [RFC PATCH v2 15/16] mm: Create the "free" file to release the previously allocated pages Juan Yescas
2026-08-06  1:09 ` [RFC PATCH v2 16/16] mm: Release resources when the page alloc hogger module exits Juan Yescas
2026-08-06  5:22 ` [RFC PATCH v2 00/16] Page Alloc Hogger Andrew Morton
2026-08-06  9:48 ` Lorenzo Stoakes (ARM) [this message]
2026-08-06 11:17   ` David Hildenbrand (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=anRRLwa3N5bVCHET@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