Date: Sat, 22 Sep 2007 09:06:13 +0200
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
Message-ID: <20070922070612.GA6125@suse.de>
Mail-Followup-To: Pavel Machek <pavel@ucw.cz>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-arch@vger.kernel.org
References: <20070913161428.343951643@strauss.suse.de> <20070913161430.686458007@strauss.suse.de> <20070918172108.GD5966@ucw.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070918172108.GD5966@ucw.cz>
Organization: SUSE LINUX Products GmbH
User-Agent: Mutt/1.5.16 (2007-06-09)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1172
Lines: 35

* 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/