From: Jingbai Ma <jingbai.ma@hp.com>
To: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>
Cc: d.hatayama@jp.fujitsu.com, kexec@lists.infradead.org,
cpw@sgi.com, jingbai.ma@hp.com
Subject: Re: [PATCH] makedumpfile: non-cyclic default
Date: Tue, 21 May 2013 10:53:52 +0800 [thread overview]
Message-ID: <519AE1C0.2060401@hp.com> (raw)
In-Reply-To: <20130521111516.af6d1f8d14f39c8d34d9d18d@mxc.nes.nec.co.jp>
On 05/21/2013 10:15 AM, Atsushi Kumagai wrote:
> On Wed, 15 May 2013 13:43:59 -0500
> Cliff Wickman<cpw@sgi.com> wrote:
>
>> From: Cliff Wickman<cpw@sgi.com>
>>
>> Make non-cyclic the default, as it is faster.
>>
>> Dumping a 1TB memory is successful with a crashkernel=512M.
>> And allow -Y on the command line, as well as --non-cylic.
>>
>> Signed-off-by: Cliff Wickman<cpw@sgi.com>
>
> This change causes the failure due to lack of memory, again.
>
> I think reliability is more important than performance, it's desirable
> that anyone can use makedumpfile safely without any considerations.
>
> Only experts who can set "crashkernel" appropriately based on physical
> memory size should use --non-cyclic option manually for performance.
>
I second leave default mode to cyclic. It's difficult to guess how much
memory the secondary kernel needed. The memory requirement from
different device driver also be very different, especially on machines
with many I/O cards.
So we don't know if the memory is enough for non-cyclic.
Once we have kernel 3.9 and kexec-tools-2.0.4, We will have enough
memory above 4GB address. And then, the next question will be how much
memory we should reserve for crashkernel.
>
> Thanks
> Atsushi Kumagai
>
>> ---
>> makedumpfile.c | 9 ++++++---
>> 1 file changed, 6 insertions(+), 3 deletions(-)
>>
>> Index: makedumpfile.mmap/makedumpfile.c
>> ===================================================================
>> --- makedumpfile.mmap.orig/makedumpfile.c
>> +++ makedumpfile.mmap/makedumpfile.c
>> @@ -8585,13 +8585,14 @@ main(int argc, char *argv[])
>> initialize_tables();
>>
>> /*
>> - * By default, makedumpfile works in constant memory space.
>> + * By default, makedumpfile makes one pass through page structures.
>> + * Use --cyclic-buffer to work in constant memory space.
>> */
>> - info->flag_cyclic = TRUE;
>> + info->flag_cyclic = FALSE;
>>
>> info->block_order = DEFAULT_ORDER;
>> message_level = DEFAULT_MSG_LEVEL;
>> - while ((opt = getopt_long(argc, argv, "b:cDd:EFfg:hi:lMpRrsvXx:", longopts,
>> + while ((opt = getopt_long(argc, argv, "b:cDd:EFfg:hi:lMpRrsvXx:Y", longopts,
>> NULL)) != -1) {
>> switch (opt) {
>> case 'A':
>> @@ -8694,6 +8695,8 @@ main(int argc, char *argv[])
>> break;
>> case 'Z':
>> info->bufsize_cyclic = atoi(optarg);
>> + if (info->bufsize_cyclic)
>> + info->flag_cyclic = TRUE;
>> break;
>> case '?':
>> MSG("Commandline parameter is invalid.\n");
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
--
Thanks,
Jingbai Ma
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2013-05-21 2:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 18:43 [PATCH] makedumpfile: non-cyclic default Cliff Wickman
2013-05-21 0:36 ` HATAYAMA Daisuke
2013-05-21 2:15 ` Atsushi Kumagai
2013-05-21 2:53 ` Jingbai Ma [this message]
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=519AE1C0.2060401@hp.com \
--to=jingbai.ma@hp.com \
--cc=cpw@sgi.com \
--cc=d.hatayama@jp.fujitsu.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