From: Baoquan <bhe@redhat.com>
To: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>
Cc: Kexec-ml <kexec@lists.infradead.org>
Subject: makefumpfile tool to estimate vmcore file size
Date: Wed, 17 Jul 2013 15:58:30 +0800 [thread overview]
Message-ID: <51E64EA6.9040209@redhat.com> (raw)
Hi Atsushi,
Our customer want us to provide a tool to estimate the required dump
file size based on the current system memory footprint. The following is
detailed requirement I tried to conclude, what's your opinion?
In customer's place there are thousands of machines and they don't want
to budget for significant increases in storage if unnecessary. This
becomes particularly expensive with large memory (1tb+) systems booting
off san disk.
Customer would like to achieve this by below example:
##########################################################
#makedumpfile -d31 -c/-l/-p
TYPE PAGES INCLUDED
Zero Page x no
Cache Without Private x no
Cache With Private x no
User Data x no
Free Page x no
Kernel Code x yes
Kernel Data x yes
Total Pages on system: 311000 (Just for example)
Total Pages included in kdump: 160000 (Just for example)
Estimated vmcore file size: 48000 (30% compression ratio)
##########################################################
By configured dump level, total pages included in kdump can be computed.
Then with option which specify a compression algorithm, an estimated
vmcore file size can be given. Though the estimated value is changed
dynamically with time, it does give user a valuable reference.
Thanks a lot
Baoquan
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2013-07-17 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 7:58 Baoquan [this message]
2013-07-24 7:06 ` makefumpfile tool to estimate vmcore file size Atsushi Kumagai
2013-08-02 3:29 ` Baoquan He
2013-08-23 9:26 ` Atsushi Kumagai
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=51E64EA6.9040209@redhat.com \
--to=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