From: Juan Yescas <jyescas@google.com>
To: 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>
Cc: jyescas@google.com, android-mm@google.com, fvdl@google.com,
tkjos@google.com, minchan@google.com, dskiba@google.com,
open list <linux-kernel@vger.kernel.org>,
"open list:MEMORY MANAGEMENT - CORE" <linux-mm@kvack.org>
Subject: [RFC PATCH 08/16] mm: Define function that creates the "nr_pages_allocs" file
Date: Thu, 23 Jul 2026 00:47:12 -0700 [thread overview]
Message-ID: <20260723074854.1013941-9-jyescas@google.com> (raw)
In-Reply-To: <20260723074854.1013941-1-jyescas@google.com>
This change implements the function that creates the
"nr_pages_allocs". This file will be used to make the allocations.
When the user wants to make an allocation, it will write
the number of allocations to this file. For example, if want
to make 56 allocations of order 9 in the Node 0, Normal Zone and Migrate
type Movable, we execute this command:
echo 56 > <sysfs>/mm/node-0/zone-Normal/order-9/migrate-Movable/nr_pages_allocs
Signed-off-by: Juan Yescas <jyescas@google.com>
---
mm/page_alloc_hogger.c | 58 ++++++++++++++++++++++++++++++++++++++++++
1 file changed, 58 insertions(+)
diff --git a/mm/page_alloc_hogger.c b/mm/page_alloc_hogger.c
index a727c4f48ffb..3ffad74a0bdf 100644
--- a/mm/page_alloc_hogger.c
+++ b/mm/page_alloc_hogger.c
@@ -127,6 +127,58 @@ struct page_alloc {
struct kmem_cache *req_alloc_cache;
struct kmem_cache *page_alloc_cache;
+
+/**
+ * req_page_alloc_write() - Allocates the pages on the requested node, zone,
+ * order and migrate type. Once the allocation is performed, a file is created
+ * to free the allocation later.
+ */
+static ssize_t req_page_alloc_write(struct file *file, const char __user *ubuf,
+ size_t cnt, loff_t *ppos)
+{
+ return cnt;
+}
+
+static const struct file_operations req_page_alloc_fops = {
+ .owner = THIS_MODULE,
+ .open = simple_open,
+ .write = req_page_alloc_write,
+};
+
+/**
+ * create_nr_pages_allocs_file() - Creates the file "nr_pages_allocs".
+ *
+ * The "nr_pages_allocs" file will be used to write the number of allocations
+ * that will be performed. When the allocations are performed, a new file for
+ * each allocation will be created in @migratedir.
+ */
+static inline int create_nr_pages_allocs_file(struct dentry *migratedir,
+ int node_idx, int zone_idx,
+ int order, int mtype)
+{
+ struct req_alloc *req;
+ struct dentry *nr_pages;
+
+ req = kmem_cache_alloc(req_alloc_cache, GFP_KERNEL);
+ if (!req) {
+ pr_err("Failed to create nr_pages_allocs_info");
+ return -ENOMEM;
+ }
+
+ req->node_idx = node_idx;
+ req->zone_idx = zone_idx;
+ req->order = order;
+ req->migrate_type = mtype;
+ req->parentdir = migratedir;
+
+ nr_pages = debugfs_create_file("nr_pages_allocs", 0644, migratedir, req,
+ &req_page_alloc_fops);
+ if (IS_ERR(nr_pages))
+ return PTR_ERR(nr_pages);
+
+ return 0;
+}
+
/**
* create_migrate_type_subdirs() - Creates a directory for each migrate type
* inside the order directory. Once the migrate type directory is created, it
@@ -138,6 +190,7 @@ static inline int create_migrate_type_subdirs(struct dentry *orderdir,
{
struct dentry *migratedir;
char dirname[24];
+ int ret;
for (int mtype = 0; mtype < MIGRATE_TYPES; mtype++) {
#ifdef CONFIG_CMA
@@ -153,6 +206,11 @@ static inline int create_migrate_type_subdirs(struct dentry *orderdir,
migratedir = debugfs_create_dir(dirname, orderdir);
if (IS_ERR(migratedir))
return PTR_ERR(migratedir);
+
+ ret = create_nr_pages_allocs_file(migratedir, node_idx,
+ zone_idx, order, mtype);
+ if (ret)
+ return ret;
}
return 0;
--
2.55.0.229.g6434b31f56-goog
next prev parent reply other threads:[~2026-07-23 7:50 UTC|newest]
Thread overview: 20+ 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 ` Juan Yescas [this message]
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)
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=20260723074854.1013941-9-jyescas@google.com \
--to=jyescas@google.com \
--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=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