From: Vivek Goyal <vgoyal@redhat.com>
To: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
Cc: dzickus@redhat.com, oomichi@mxs.nes.nec.co.jp,
kumagai-atsushi@mxc.nes.nec.co.jp, kexec@lists.infradead.org
Subject: Re: makedumpfile memory usage grows with system memory size
Date: Thu, 5 Apr 2012 10:34:39 -0400 [thread overview]
Message-ID: <20120405143439.GA23999@redhat.com> (raw)
In-Reply-To: <20120405.155211.347142878.d.hatayama@jp.fujitsu.com>
On Thu, Apr 05, 2012 at 03:52:11PM +0900, HATAYAMA Daisuke wrote:
[..]
> * Bad performance is free pages only. Cache, cache private, user and
> zero pages are processed per range of memory in good performance.
Hi Daisuke-san,
I am wondering why can't we walk through the memmap array and look into
struct page for figuring out if page is free or not. Looks like that
in the past we used to have PG_buddy flag and same information possibly
could be retrieved by looking at page->_count field.
So I am just curious that why do we walk through free pages list to figure
out free pages instead of looking at "struct page".
Thanks
Vivek
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2012-04-05 14:34 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 [this message]
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
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=20120405143439.GA23999@redhat.com \
--to=vgoyal@redhat.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=dzickus@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
--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