From: Don Zickus <dzickus@redhat.com>
To: Ken'ichi Ohmichi <oomichi@mxs.nes.nec.co.jp>
Cc: kexec@lists.infradead.org
Subject: Re: makedumpfile memory usage grows with system memory size
Date: Thu, 29 Mar 2012 09:05:14 -0400 [thread overview]
Message-ID: <20120329130514.GK18218@redhat.com> (raw)
In-Reply-To: <20120329170918.4223e816.oomichi@mxs.nes.nec.co.jp>
Hi Ken'ichi-san,
On Thu, Mar 29, 2012 at 05:09:18PM +0900, Ken'ichi Ohmichi wrote:
>
> Hi Don-san,
>
> On Wed, 28 Mar 2012 17:22:04 -0400
> Don Zickus <dzickus@redhat.com> wrote:
> >
> > I was talking to Vivek about kdump memory requirements and he mentioned
> > that they vary based on how much system memory is used.
> >
> > I was interested in knowing why that was and again he mentioned that
> > makedumpfile needed lots of memory if it was running on a large machine
> > (for example 1TB of system memory).
> >
> > Looking through the makedumpfile README and using what Vivek remembered of
> > makedumpfile, we gathered that as the number of pages grows, the more
> > makedumpfile has to temporarily store the information in memory. The
> > possible reason was to calculate the size of the file before it was copied
> > to its final destination?
>
> makedumpfile uses the system memory of 2nd-kernel for a bitmap if RHEL.
> The bitmap represents each page of 1st-kernel is excluded or not.
> So the bitmap size depends on 1st-kernel's system memory.
>
> makedumpfile creates a file /tmp/kdump_bitmapXXXXXX as the bitmap,
> and the file is created on 2nd-kernel's memory if RHEL, because
> RHEL does not mount a root filesystem when 2nd-kernel is running.
Ok.
>
>
> > I was curious if that was true and if it was, would it be possible to only
> > process memory in chunks instead of all at once.
> >
> > The idea is that a machine with 4Gigs of memory should consume the same
> > the amount of kdump runtime memory as a 1TB memory system.
> >
> > Just trying to research ways to keep the memory requirements consistent
> > across all memory ranges.
>
> I think the above purpose is good, and I don't have any idea for reducing
> the bitmap size. And now I am out of makedumpfile development.
> Kumagai-san is the makedumpfile maintainer now, and he will help you.
Thanks for the feedback, I'll wait for Kumagai-san's response then.
Cheers,
Don
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2012-03-29 13:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 21:22 makedumpfile memory usage grows with system memory size Don Zickus
2012-03-29 8:09 ` Ken'ichi Ohmichi
2012-03-29 12:56 ` HATAYAMA Daisuke
2012-03-29 13:25 ` Don Zickus
2012-03-30 0:51 ` HATAYAMA Daisuke
2012-04-02 7:46 ` Atsushi Kumagai
2012-04-05 6:52 ` HATAYAMA Daisuke
2012-04-05 14:34 ` Vivek Goyal
2012-04-06 1:12 ` HATAYAMA Daisuke
2012-04-06 8:59 ` Atsushi Kumagai
2012-04-06 9:29 ` HATAYAMA Daisuke
2012-04-09 18:57 ` Vivek Goyal
2012-04-09 23:58 ` HATAYAMA Daisuke
2012-04-10 12:52 ` Vivek Goyal
2012-04-12 3:40 ` Atsushi Kumagai
2012-04-12 7:47 ` HATAYAMA Daisuke
[not found] ` <20120427164649.9932a33f.kumagai-atsushi@mxc.nes.nec.co.jp>
2012-04-27 12:52 ` Don Zickus
2012-05-11 1:19 ` Atsushi Kumagai
2012-05-11 13:26 ` Don Zickus
2012-05-15 5:57 ` Atsushi Kumagai
2012-05-15 12:35 ` Don Zickus
2012-04-27 13:33 ` Vivek Goyal
2012-05-14 5:44 ` HATAYAMA Daisuke
2012-05-16 8:02 ` Atsushi Kumagai
2012-05-17 0:21 ` HATAYAMA Daisuke
2012-04-09 19:00 ` Vivek Goyal
2012-03-29 13:05 ` Don Zickus [this message]
2012-03-30 9:43 ` Atsushi Kumagai
2012-03-30 13:19 ` Don Zickus
2012-04-02 17:15 ` Michael Holzheu
2012-04-06 8:09 ` Atsushi Kumagai
2012-04-11 8:04 ` Michael Holzheu
2012-04-12 8:49 ` Atsushi Kumagai
-- strict thread matches above, loose matches on Subject: below --
2012-04-02 6:53 tachibana
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=20120329130514.GK18218@redhat.com \
--to=dzickus@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=oomichi@mxs.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