From: Vivek Goyal <vgoyal@redhat.com>
To: Baoquan He <bhe@redhat.com>
Cc: kumagai-atsushi@mxc.nes.nec.co.jp, kexec@lists.infradead.org
Subject: Re: [PATCH 7/7] add a new interface to show the memory usage of 1st kernel
Date: Fri, 11 Jul 2014 10:26:39 -0400 [thread overview]
Message-ID: <20140711142639.GG15611@redhat.com> (raw)
In-Reply-To: <1405062964-11406-7-git-send-email-bhe@redhat.com>
On Fri, Jul 11, 2014 at 03:16:04PM +0800, Baoquan He wrote:
> Recently people complained that they don't decide how much disk size
> need be reserved for kdump storing. E.g there are lots of machines
> with different memory size, if the memory usage information of current
> system can be shown, that can help them to make an estimate how much
> storage space need be reserved.
>
> In this patch, a new interface is added into makedumpfile. With the
> help of this, people can know the page number of memory in different
> use. The implementation is analyzing the "System Ram" and "kernel text"
> program segment of /proc/kcore excluding the crashkernel range, then
> calculating the page number of different kind per vmcoreinfo.
>
> The print is like below:
> ->$ ./makedumpfile --mem-usage /proc/kcore
> Excluding unnecessary pages : [100.0 %] |
>
> Page number of memory in different use
Hi Bao,
How about priting number of pages in decimal numbers. Humans read decimal
numbers much better.
> --------------------------------------------------
> TYPE PAGES EXCLUDABLE DESCRIPTION
> pfn_zero 0x0000000000000000 yes Pages filled with zero
I am wondering if we display TYPE of page as follows. Will it be more
redable
ZERO
CACHE
CACHE_PRIVATE
..
..
> pfn_cache 0x000000000002b19f yes Cache pages
> pfn_cache_private 0x0000000000042526 yes Cache pages + private
> pfn_user 0x0000000000026bc3 yes User process data pages
How about calling them just "User process pages" and not "user process
data pages" I am assuming that they could contain text too.
> pfn_free 0x0000000000133f79 yes Free pages
> pfn_hwpoison 0x0000000000000000 yes Hwpoison pages
> pfn_kernel_data 0x000000000001dd56 no Dumpable kernel data
>
> Total pages on system: 0x00000000001e5f57
> Excludable pages: 0x00000000001c8201
> Memory Hole: 0x00000000000386a9
What is "Memory Hole" ?
> --------------------------------------------------
> Total pages: 0x000000000021e600
How this total pages is different from "Total pages on system"?
Thanks
Vivek
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2014-07-11 14:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 7:15 [PATCH 1/7] initialize pfn_memhole in get_num_dumpable_cyclic Baoquan He
2014-07-11 7:15 ` [PATCH 2/7] functions to get crashkernel memory range Baoquan He
2014-07-11 7:16 ` [PATCH 3/7] preparation functions for parsing vmcoreinfo Baoquan He
2014-07-11 7:16 ` [PATCH 4/7] set vmcoreinfo for kcore Baoquan He
2014-07-11 7:16 ` [PATCH 5/7] prepare the dump loads for kcore analysis Baoquan He
2014-07-23 7:20 ` Atsushi Kumagai
2014-07-23 8:02 ` bhe
2014-07-11 7:16 ` [PATCH 6/7] implement a function to print the memory usage Baoquan He
2014-07-11 7:16 ` [PATCH 7/7] add a new interface to show the memory usage of 1st kernel Baoquan He
2014-07-11 7:27 ` [PATCH v2] " Baoquan He
2014-07-23 7:20 ` Atsushi Kumagai
2014-07-23 8:01 ` bhe
2014-07-11 7:35 ` [PATCH 7/7] " Baoquan He
2014-07-11 14:26 ` Vivek Goyal [this message]
2014-07-11 14:35 ` Baoquan He
2014-07-11 14:44 ` Vivek Goyal
2014-07-11 14:35 ` Vivek Goyal
2014-07-11 14:39 ` Baoquan He
2014-07-11 14:46 ` Vivek Goyal
2014-07-14 5:22 ` Baoquan He
2014-07-11 14:19 ` [PATCH 1/7] initialize pfn_memhole in get_num_dumpable_cyclic Vivek Goyal
2014-07-11 14:28 ` Baoquan He
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=20140711142639.GG15611@redhat.com \
--to=vgoyal@redhat.com \
--cc=bhe@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
/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