From: Don Zickus <dzickus@redhat.com>
To: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>
Cc: oomichi@mxs.nes.nec.co.jp, d.hatayama@jp.fujitsu.com,
kexec@lists.infradead.org, vgoyal@redhat.com
Subject: Re: makedumpfile memory usage grows with system memory size
Date: Tue, 15 May 2012 08:35:38 -0400 [thread overview]
Message-ID: <20120515123538.GR32472@redhat.com> (raw)
In-Reply-To: <20120515145705.d6daeb68.kumagai-atsushi@mxc.nes.nec.co.jp>
On Tue, May 15, 2012 at 02:57:05PM +0900, Atsushi Kumagai wrote:
> Hello Don,
>
> On Fri, 11 May 2012 09:26:01 -0400
> Don Zickus <dzickus@redhat.com> wrote:
>
> > > Thank you for your reply, Don, Vivek.
> > >
> > > As Don said, I tried to change the method to exclude free pages and
> > > planed to resolve the memory consumption issue after it, because
> > > parsing free list repeatedly may cause a performance issue.
> > >
> > > However, I'm thinking that to fix the size of memory consumption is more
> > > important than to resolve a performance issue for large system.
> > >
> > > So I'm afraid that I would like to change the plan as:
> > >
> > > 1. Implement "iterating filtering processing" to fix the size of memory
> > > consumption. At this stage, makedumpfile will parse free list repeatedly
> > > even though it may cause a performance issue.
> > >
> > > 2. Take care of the performance issue after the 1st step.
> >
> > Hello Atsushi-san,
> >
> > Hmm. The problem with the free list is that the addresses are in random
> > order, hence the reason to parse it repeatedly, correct?
>
> Yes.
>
> > I figured, now that you have a solution to parse the addresses in a linear
> > way (the changes you made a couple of weeks ago), you would just continue
> > with that. With that complete, we can look at the performance issues and
> > solve them then.
> >
> > But it is up to you. You are willing to do the work, so I will defer to
> > your judgement on how best to proceed. :-)
>
> What I wanted to tell you was I want to resolve the memory consumption issue
> as soon as possible. In other words, I think the method to exclude free pages
> is not so important.
> I'll continue to work with the method which is easy to implement.
Ok. I look forward to your results. Thanks for your effort.
Cheers,
Don
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2012-05-15 12:35 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 [this message]
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
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=20120515123538.GR32472@redhat.com \
--to=dzickus@redhat.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
--cc=oomichi@mxs.nes.nec.co.jp \
--cc=vgoyal@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.