All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Walle <bwalle@suse.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-arch@vger.kernel.org, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 7/7] Add documentation for extended crashkernel syntax
Date: Sat, 22 Sep 2007 09:06:13 +0200	[thread overview]
Message-ID: <20070922070612.GA6125@suse.de> (raw)
In-Reply-To: <20070918172108.GD5966@ucw.cz>

* Pavel Machek <pavel@ucw.cz> [2007-09-18 19:21]:
> > This adds the documentation for the extended crashkernel syntax into
> > Documentation/kdump/kdump.txt.
> 
> Should you also update kernel-parameters.txt?

Ok, I'll do.

> > +For example:
> > +
> > +    crashkernel=512M-2G:64M,2G-:128M
> > +
> > +This would mean:
> > +
> > +    1) if the RAM is smaller than 512M, then don't reserve anything
> > +       (this is the "rescue" case)
> > +    2) if the RAM size is between 512M and 2G, then reserve 64M
> > +    3) if the RAM size is larger than 2G, then reserve 128M
> 
> Why is this useful? I mean... if 64M is enough to save a dump, why use
> 128M? ...or does the required size somehow scale with memory in
> machine? (pagetables?)

A bit, yes (ELF core headers, DISCONT memory, per-CPU data), but
consider also that saving may be faster if you have more RAM (e.g.
saving over SSH, encryption, ...).


Thanks,
   Bernhard

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Bernhard Walle <bwalle@suse.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-arch@vger.kernel.org
Subject: Re: [patch 7/7] Add documentation for extended crashkernel syntax
Date: Sat, 22 Sep 2007 09:06:13 +0200	[thread overview]
Message-ID: <20070922070612.GA6125@suse.de> (raw)
In-Reply-To: <20070918172108.GD5966@ucw.cz>

* Pavel Machek <pavel@ucw.cz> [2007-09-18 19:21]:
> > This adds the documentation for the extended crashkernel syntax into
> > Documentation/kdump/kdump.txt.
> 
> Should you also update kernel-parameters.txt?

Ok, I'll do.

> > +For example:
> > +
> > +    crashkernel=512M-2G:64M,2G-:128M
> > +
> > +This would mean:
> > +
> > +    1) if the RAM is smaller than 512M, then don't reserve anything
> > +       (this is the "rescue" case)
> > +    2) if the RAM size is between 512M and 2G, then reserve 64M
> > +    3) if the RAM size is larger than 2G, then reserve 128M
> 
> Why is this useful? I mean... if 64M is enough to save a dump, why use
> 128M? ...or does the required size somehow scale with memory in
> machine? (pagetables?)

A bit, yes (ELF core headers, DISCONT memory, per-CPU data), but
consider also that saving may be faster if you have more RAM (e.g.
saving over SSH, encryption, ...).


Thanks,
   Bernhard

  reply	other threads:[~2007-09-22  7:06 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13 16:14 [patch 0/7] Add extended crashkernel command line syntax Bernhard Walle
2007-09-13 16:14 ` Bernhard Walle
2007-09-13 16:14 ` [patch 1/7] Extended crashkernel command line Bernhard Walle
2007-09-13 16:14   ` Bernhard Walle
2007-09-19 22:32   ` Andrew Morton
2007-09-19 22:32     ` Andrew Morton
2007-09-13 16:14 ` [patch 2/7] Use extended crashkernel command line on i386 Bernhard Walle
2007-09-13 16:14   ` Bernhard Walle
2007-09-18  4:36   ` Vivek Goyal
2007-09-18  4:36     ` Vivek Goyal
2007-09-13 16:14 ` [patch 3/7] Use extended crashkernel command line on x86_64 Bernhard Walle
2007-09-13 16:14   ` Bernhard Walle
2007-09-19 22:33   ` Andrew Morton
2007-09-19 22:33     ` Andrew Morton
2007-09-20 17:19     ` Bernhard Walle
2007-09-20 17:19       ` Bernhard Walle
2007-09-13 16:14 ` [patch 4/7] Use extended crashkernel command line on ia64 Bernhard Walle
2007-09-13 16:14   ` Bernhard Walle
2007-09-13 16:14   ` Bernhard Walle
2007-09-13 16:14 ` [patch 5/7] Use extended crashkernel command line on ppc64 Bernhard Walle
2007-09-13 16:14   ` Bernhard Walle
2007-09-13 16:14   ` Bernhard Walle
2007-09-13 16:14 ` [patch 6/7] Use extended crashkernel command line on sh Bernhard Walle
2007-09-13 16:14   ` Bernhard Walle
2007-09-14  3:30   ` Paul Mundt
2007-09-14  3:30     ` Paul Mundt
2007-09-13 16:14 ` [patch 7/7] Add documentation for extended crashkernel syntax Bernhard Walle
2007-09-13 16:14   ` Bernhard Walle
2007-09-18 17:21   ` Pavel Machek
2007-09-18 17:21     ` Pavel Machek
2007-09-22  7:06     ` Bernhard Walle [this message]
2007-09-22  7:06       ` Bernhard Walle
  -- strict thread matches above, loose matches on Subject: below --
2007-09-20 17:18 [patch 0/7] Add extended crashkernel command line syntax Bernhard Walle
2007-09-20 17:18 ` [patch 7/7] Add documentation for extended crashkernel syntax Bernhard Walle
2007-09-20 17:18   ` Bernhard Walle
2007-09-25 18:22 [patch 0/7] Add extended crashkernel command line syntax Bernhard Walle
2007-09-25 18:23 ` [patch 7/7] Add documentation for extended crashkernel syntax Bernhard Walle
2007-09-25 18:23   ` Bernhard Walle

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=20070922070612.GA6125@suse.de \
    --to=bwalle@suse.de \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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.