From: Ye Liu <ye.liu@linux.dev>
To: Andrew Morton <akpm@linux-foundation.org>,
Uladzislau Rezki <urezki@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Ye Liu <liuye@kylinos.cn>
Subject: [PATCH v2 3/3] mm/vmalloc: extract show_busy_info from vmalloc_info_show
Date: Tue, 15 Sep 2026 10:43:32 +0800 [thread overview]
Message-ID: <20260915-vmalloc_study-v2-3-cc4dfe635e22@linux.dev> (raw)
In-Reply-To: <20260915-vmalloc_study-v2-0-cc4dfe635e22@linux.dev>
From: Ye Liu <liuye@kylinos.cn>
Extract the busy vmap area iteration into show_busy_info, mirroring
the existing show_purge_info pattern.
Signed-off-by: Ye Liu <liuye@kylinos.cn>
Reviewed-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
---
mm/vmalloc.c | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index 973d15ef4f3e..e09d6c8c8b35 100644
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -5345,7 +5345,7 @@ static void show_purge_info(struct seq_file *m)
}
}
-static int vmalloc_info_show(struct seq_file *m, void *p)
+static void show_busy_info(struct seq_file *m)
{
struct vmap_node *vn;
struct vmap_area *va;
@@ -5415,12 +5415,18 @@ static int vmalloc_info_show(struct seq_file *m, void *p)
spin_unlock(&vn->busy.lock);
}
+ if (IS_ENABLED(CONFIG_NUMA))
+ kfree(counters);
+}
+
+static int vmalloc_info_show(struct seq_file *m, void *p)
+{
+ show_busy_info(m);
+
/*
* As a final step, dump "unpurged" areas.
*/
show_purge_info(m);
- if (IS_ENABLED(CONFIG_NUMA))
- kfree(counters);
return 0;
}
--
2.25.1
prev parent reply other threads:[~2026-09-15 2:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 2:43 [PATCH v2 0/3] mm/vmalloc: minor cleanups Ye Liu
2026-09-15 2:43 ` [PATCH v2 1/3] mm/vmalloc: group xa_init with vbq field initializations Ye Liu
2026-09-15 2:43 ` [PATCH v2 2/3] mm/vmalloc: extract vmap_insert_free_area helper Ye Liu
2026-09-15 2:43 ` Ye Liu [this message]
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=20260915-vmalloc_study-v2-3-cc4dfe635e22@linux.dev \
--to=ye.liu@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuye@kylinos.cn \
--cc=urezki@gmail.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®