| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20070922070612.GA6125@suse.de> Date: Sat, 22 Sep 2007 09:06:13 +0200 From: Bernhard Walle <bwalle@...e.de> To: Pavel Machek <pavel@....cz> Cc: kexec@...ts.infradead.org, linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org Subject: Re: [patch 7/7] Add documentation for extended crashkernel syntax * Pavel Machek <pavel@....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@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists