From: Yafang Shao <laoar.shao@gmail.com>
To: mhocko@suse.com, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, shaoyafang@didiglobal.com,
Yafang Shao <laoar.shao@gmail.com>
Subject: [PATCH v2 1/3] mm/vmstat: expose min_slab_pages in /proc/zoneinfo
Date: Mon, 27 May 2019 19:52:52 +0800 [thread overview]
Message-ID: <1558957974-23341-2-git-send-email-laoar.shao@gmail.com> (raw)
In-Reply-To: <1558957974-23341-1-git-send-email-laoar.shao@gmail.com>
On one of our servers, we find the dentry is continuously growing
without shrinking. We're not sure whether that is because reclaimable
slab is still less than min_slab_pages.
So if we expose min_slab_pages, it would be easy to compare.
As we can set min_slab_ratio with sysctl, we should expose the effective
min_slab_pages to user as well.
That is same with min_unmapped_pages.
Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
---
mm/vmstat.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/mm/vmstat.c b/mm/vmstat.c
index a7d4933..bb76cfe 100644
--- a/mm/vmstat.c
+++ b/mm/vmstat.c
@@ -1549,7 +1549,15 @@ static void zoneinfo_show_print(struct seq_file *m, pg_data_t *pgdat,
NR_VM_NUMA_STAT_ITEMS],
node_page_state(pgdat, i));
}
+
+#ifdef CONFIG_NUMA
+ seq_printf(m, "\n %-12s %lu", "min_slab",
+ pgdat->min_slab_pages);
+ seq_printf(m, "\n %-12s %lu", "min_unmapped",
+ pgdat->min_unmapped_pages);
+#endif
}
+
seq_printf(m,
"\n pages free %lu"
"\n min %lu"
--
1.8.3.1
next prev parent reply other threads:[~2019-05-27 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 11:52 [PATCH v2 0/3] mm: improvement in shrink slab Yafang Shao
2019-05-27 11:52 ` Yafang Shao [this message]
2019-05-27 11:52 ` [PATCH v2 2/3] mm/vmscan: change return type of shrink_node() to void Yafang Shao
2019-05-27 11:52 ` [PATCH v2 3/3] mm/vmscan: shrink slab in node reclaim Yafang Shao
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=1558957974-23341-2-git-send-email-laoar.shao@gmail.com \
--to=laoar.shao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=shaoyafang@didiglobal.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;
as well as URLs for NNTP newsgroup(s).