From: Jaewon Kim <jaewon31.kim@samsung.com>
To: adobriyan@gmail.com, akpm@linux-foundation.org,
labbott@redhat.com, sumit.semwal@linaro.org, minchan@kernel.org,
ngupta@vflare.org, sergey.senozhatsky.work@gmail.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
jaewon31.kim@gmail.com, Jaewon Kim <jaewon31.kim@samsung.com>
Subject: [RFC PATCH 2/3] mm: zsmalloc: include zs page size in proc/meminfo
Date: Wed, 11 Mar 2020 12:44:40 +0900 [thread overview]
Message-ID: <20200311034441.23243-3-jaewon31.kim@samsung.com> (raw)
In-Reply-To: <20200311034441.23243-1-jaewon31.kim@samsung.com>
On most of recent Android device use DRAM memory based compressed swap
to save free memory. And the swap device size is also big enough.
The zsmalloc page size is alread shown on vmstat by commit 91537fee0013
("mm: add NR_ZSMALLOC to vmstat"). If the size is also shown in
/proc/meminfo, it will be better to see system wide memory usage at a
glance.
To include heap size, use register_extra_meminfo introduced in previous
patch.
i.e) cat /proc/meminfo | grep ZsPages
IonSystemHeap: 242620 kB
ZsPages: 203860 kB
i.e.) show_mem on oom
<6>[ 420.856428] Mem-Info:
<6>[ 420.856433] ZsPages:44114kB
Signed-off-by: Jaewon Kim <jaewon31.kim@samsung.com>
---
mm/zsmalloc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c
index 22d17ecfe7df..9e45d7e0cd69 100644
--- a/mm/zsmalloc.c
+++ b/mm/zsmalloc.c
@@ -2566,6 +2566,7 @@ static int __init zs_init(void)
zs_stat_init();
+ register_extra_meminfo(&vm_zone_stat[NR_ZSPAGES], 0, "ZsPages");
return 0;
hp_setup_fail:
@@ -2583,6 +2584,7 @@ static void __exit zs_exit(void)
cpuhp_remove_state(CPUHP_MM_ZS_PREPARE);
zs_stat_exit();
+ unregister_extra_meminfo(&vm_zone_stat[NR_ZSPAGES]);
}
module_init(zs_init);
--
2.13.7
next prev parent reply other threads:[~2020-03-11 3:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200311034454epcas1p2ef0c0081971dd82282583559398e58b2@epcas1p2.samsung.com>
2020-03-11 3:44 ` [RFC PATCH 0/3] meminfo: introduce extra meminfo Jaewon Kim
[not found] ` <CGME20200311034454epcas1p184680d40f89d37eec7f934074c4a9fcf@epcas1p1.samsung.com>
2020-03-11 3:44 ` [RFC PATCH 1/3] proc/meminfo: " Jaewon Kim
2020-03-11 6:18 ` Sergey Senozhatsky
2020-03-11 6:25 ` Sergey Senozhatsky
2020-03-11 6:30 ` Jaewon Kim
2020-03-11 17:35 ` Alexey Dobriyan
2020-03-13 4:53 ` Jaewon Kim
[not found] ` <CGME20200311034454epcas1p13f7806e51b19c7848148c20ce3841b1b@epcas1p1.samsung.com>
2020-03-11 3:44 ` Jaewon Kim [this message]
[not found] ` <CGME20200311034454epcas1p46f44b4c1e75fa52b7598749566228a11@epcas1p4.samsung.com>
2020-03-11 3:44 ` [RFC PATCH 3/3] android: ion: include system heap size in proc/meminfo Jaewon Kim
2020-03-11 7:25 ` [RFC PATCH 0/3] meminfo: introduce extra meminfo Leon Romanovsky
2020-03-13 4:39 ` Jaewon Kim
2020-03-13 7:21 ` Leon Romanovsky
2020-03-13 15:19 ` Vlastimil Babka
2020-03-13 17:48 ` Leon Romanovsky
2020-03-16 4:07 ` Jaewon Kim
2020-03-16 8:31 ` Leon Romanovsky
2020-03-17 3:04 ` Jaewon Kim
2020-03-17 14:37 ` Leon Romanovsky
2020-03-18 8:58 ` Jaewon Kim
2020-03-18 10:58 ` Leon Romanovsky
2020-03-20 10:00 ` Dave Young
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=20200311034441.23243-3-jaewon31.kim@samsung.com \
--to=jaewon31.kim@samsung.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jaewon31.kim@gmail.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sumit.semwal@linaro.org \
/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