Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
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:46:27 -0400	[thread overview]
Message-ID: <20140711144627.GJ15611@redhat.com> (raw)
In-Reply-To: <20140711143945.GC5851@dhcp-17-102.nay.redhat.com>

On Fri, Jul 11, 2014 at 10:39:45PM +0800, Baoquan He wrote:
> On 07/11/14 at 10:35am, Vivek Goyal wrote:
> > On Fri, Jul 11, 2014 at 03:16:04PM +0800, Baoquan He wrote:
> > > ->$ ./makedumpfile  --mem-usage  /proc/kcore
> > > Excluding unnecessary pages        : [100.0 %] |
> > > 
> > > Page number of memory in different use
> > > --------------------------------------------------
> > > TYPE			PAGES			EXCLUDABLE	DESCRIPTION
> > > pfn_zero		0x0000000000000000	yes		Pages filled with zero
> > > pfn_cache		0x000000000002b19f	yes		Cache pages
> > > pfn_cache_private	0x0000000000042526	yes		Cache pages + private
> > > pfn_user		0x0000000000026bc3	yes		User process data pages
> > > pfn_free		0x0000000000133f79	yes		Free pages
> > > pfn_hwpoison		0x0000000000000000	yes		Hwpoison pages
> > 
> > Is there a need to display hwpoison pages? I think they are excluded by
> > default. Otherwise reading them might kill makedumpfile process.
> 
> You are right, hwpoison pages are excluded by default. But it truly
> calculated in makedumpfile. I will change it as non-excludable like
> below:
> 
> TYPE			PAGES			EXCLUDABLE	DESCRIPTION
> pfn_hwpoison		0x0000000000000000	No		Hwpoison pages

I think we don't have to display hwpoison pages. It is of no use. Let us
just display the pages which can be excluded using various filtering
levels and total number of pages (without memory hole).

That way people can do some math.

amount of disk space required = total_pages - filtered pages;

Thanks
Vivek

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2014-07-11 14:46 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
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 [this message]
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=20140711144627.GJ15611@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