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 15/16] mm: Create the "free" file to release the previously allocated pages
Date: Thu, 23 Jul 2026 00:47:19 -0700 [thread overview]
Message-ID: <20260723074854.1013941-16-jyescas@google.com> (raw)
In-Reply-To: <20260723074854.1013941-1-jyescas@google.com>
This change creates the "free" file and defines its file_operations
to release the previously allocated pages. To release an allocation,
the user will run:
echo <file name> > /sys/kernel/debug/mm/free
Signed-off-by: Juan Yescas <jyescas@google.com>
---
mm/page_alloc_hogger.c | 41 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 41 insertions(+)
diff --git a/mm/page_alloc_hogger.c b/mm/page_alloc_hogger.c
index e65aac881ec7..5fe9c545e884 100644
--- a/mm/page_alloc_hogger.c
+++ b/mm/page_alloc_hogger.c
@@ -83,6 +83,7 @@
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
+#include <linux/atomic.h>
#include <linux/errno.h>
#include <linux/debugfs.h>
#include <linux/gfp.h>
@@ -94,6 +95,7 @@
#include <linux/nodemask.h>
#include <linux/printk.h>
#include <linux/slab.h>
+#include <linux/xarray.h>
struct dentry *mmdir;
@@ -331,6 +333,37 @@ static const struct file_operations req_page_alloc_fops = {
.write = req_page_alloc_write,
};
+/**
+ * free_page_alloc_write() - free the previously allocated pages.
+ * @file: File where the user is writing.
+ * @ubuf: Contains the name of the file the user wants to delete and have the
+ * memory associated with that file freed.
+ * @cnt: Size of @ubuf.
+ * @ppos: Current position in the file.
+ */
+static ssize_t free_page_alloc_write(struct file *file,
+ const char __user *ubuf, size_t cnt,
+ loff_t *ppos)
+{
+ int ret;
+ unsigned long alloc_id;
+
+ ret = kstrtoul_from_user(ubuf, cnt, 10, &alloc_id);
+ if (ret)
+ return ret;
+
+ ret = free_alloc_helper(alloc_id);
+ if (ret)
+ return ret;
+
+ return cnt;
+}
+
+static const struct file_operations free_page_alloc_fops = {
+ .owner = THIS_MODULE,
+ .write = free_page_alloc_write,
+};
+
/**
* create_nr_pages_allocs_file() - Creates the file "nr_pages_allocs".
*
@@ -501,6 +534,7 @@ static inline int create_nodes_subdirs(struct dentry *mmdir)
static int __init page_alloc_hogger_debugfs_init(void)
{
+ struct dentry *free_file;
int ret;
req_alloc_cache = kmem_cache_create(
@@ -532,6 +566,13 @@ static int __init page_alloc_hogger_debugfs_init(void)
if (ret)
goto clean_dir;
+ free_file = debugfs_create_file("free", 0644, mmdir, NULL,
+ &free_page_alloc_fops);
+ if (IS_ERR(free_file)) {
+ ret = PTR_ERR(free_file);
+ goto clean_dir;
+ }
+
return 0;
clean_dir:
--
2.55.0.229.g6434b31f56-goog
next prev parent reply other threads:[~2026-07-23 7:51 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 ` [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 ` Juan Yescas [this message]
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-16-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