From: Cliff Wickman <cpw@sgi.com>
To: d.hatayama@jp.fujitsu.com, kumagai-atsushi@mxc.nes.nec.co.jp,
kexec@lists.infradead.org
Cc: lisa.mitchell@hp.com
Subject: Re: [PATCH v2] makedumpfile: request the kernel do page scans
Date: Mon, 7 Jan 2013 07:39:35 -0600 [thread overview]
Message-ID: <20130107133935.GA1207@sgi.com> (raw)
In-Reply-To: <E1TbGZV-0008DR-Tb@eag09.americas.sgi.com>
An update on testing thise patches:
> This version of the patch improves the consolidation of the mem_map table
> that is passed to the kernel. See make_kernel_mmap().
> Particularly the seemingly duplicate pfn ranges generated on an older
> (2.6.32-based, rhel6) kernel.
On a 2TB machine (idle) machine:
the crash kernel ran successfully in 512M
the scan for unnecessary pages takes about 40 seconds
it was a single scan, not cyclic
On a 16TB machine (idle) machine:
the crash kernel ran successfully in 512M
there is a pause of about 4 minutes during makedumpfile initialization
the scan for unnecessary pages takes about 4.8 minutes
it was a single scan, not cyclic
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-01-07 13:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 20:06 [PATCH v2] makedumpfile: request the kernel do page scans Cliff Wickman
2012-11-22 1:43 ` Hatayama, Daisuke
2012-11-22 14:07 ` HATAYAMA Daisuke
2013-01-07 13:39 ` Cliff Wickman [this message]
2013-01-09 15:09 ` HATAYAMA Daisuke
[not found] ` <20130111223034.GA2154@sgi.com>
2013-01-17 1:38 ` HATAYAMA Daisuke
-- strict thread matches above, loose matches on Subject: below --
2013-01-04 16:20 Cliff Wickman
2013-01-16 12:15 ` Lisa Mitchell
2013-01-16 12:51 ` Lisa Mitchell
2013-01-16 17:50 ` Cliff Wickman
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=20130107133935.GA1207@sgi.com \
--to=cpw@sgi.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
--cc=lisa.mitchell@hp.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.