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] Makedumpfile: vmcore size estimate
Date: Mon, 23 Jun 2014 08:36:54 -0400	[thread overview]
Message-ID: <20140623123654.GA29112@redhat.com> (raw)
In-Reply-To: <1402490345-18656-1-git-send-email-bhe@redhat.com>

On Wed, Jun 11, 2014 at 08:39:05PM +0800, Baoquan He wrote:
> User want to get a rough estimate of vmcore size, then they can decide
> how much storage space is reserved for vmcore dumping. This can help them
> to deploy their machines better, possibly hundreds of machines.
> 
> In this draft patch, a new configuration option is added,
>     "--vmcore-estimate"
> User can execute below command to get a dumped kcore. Since kcore is a
> elf file to map the whole memory of current kernel, it's  equal to the
> memory of crash kernel though it's not exact. Content of kcore is dynamic
> though /proc/vmcore is fixed once crash happened. But for vmcore size
> estimate, it is better enough.
> 
> sudo makedumpfile -E -d 31 --vmcore-estimate /proc/kcore /var/crash/kcore-dump
> 
> Questions:
> 1. Or we can get the dumpable page numbers only, then calculate the estimated
> vmcore size by a predifined factor if it's kdump compressed dumping. E.g if
> lzo dump, we assume the compression ratio is 45%, then the estimate size is
> equal to: (dumpable page numbers) * 4096* 45%.

I think that we can probably not guess the saving from compression.
Compression ratio varies based on content of page. So if we keep it simple
and just calculate the number of pages which will be dumped and multiply
it by page size, that number will be much more accurate (for current
system).

Thanks
Vivek

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

  parent reply	other threads:[~2014-06-23 12:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11 12:39 [PATCH] Makedumpfile: vmcore size estimate Baoquan He
2014-06-11 13:57 ` Baoquan He
2014-06-20  1:07   ` Atsushi Kumagai
2014-06-20  1:58     ` bhe
2014-06-20  2:33     ` bhe
2014-06-23 12:57     ` Vivek Goyal
2014-06-26  8:21       ` Atsushi Kumagai
2014-06-26 12:31         ` Vivek Goyal
2014-07-02  0:25           ` Atsushi Kumagai
2014-07-02  8:13             ` bhe
2014-07-04  1:53               ` HATAYAMA, Daisuke
2014-07-04  9:44                 ` bhe
2014-07-11 13:51                 ` Vivek Goyal
2014-06-23 12:36 ` Vivek Goyal [this message]
2014-06-23 13:05   ` Baoquan He
2014-06-23 13:55     ` Anders Rayner-Karlsson

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=20140623123654.GA29112@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