From: ebiederm@xmission.com (Eric W. Biederman)
To: Bernhard Walle <bernhard.walle@gmx.de>
Cc: Amerigo Wang <amwang@redhat.com>,
Neil Horman <nhorman@redhat.com>,
linux-kernel@vger.kernel.org, tony.luck@intel.com,
linux-ia64@vger.kernel.org, akpm@linux-foundation.org,
Ingo Molnar <mingo@elte.hu>,
Anton Vorontsov <avorontsov@ru.mvista.com>,
Andi Kleen <andi@firstfloor.org>,
Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: [Patch 0/7] Implement crashkernel=auto
Date: Fri, 07 Aug 2009 15:16:43 -0700 [thread overview]
Message-ID: <m1tz0jmfqs.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <4A7C9D48.3030405@gmx.de> (Bernhard Walle's message of "Fri\, 07 Aug 2009 23\:31\:52 +0200")
Bernhard Walle <bernhard.walle@gmx.de> writes:
> Eric W. Biederman schrieb:
>>
>> With the current set of crashkernel= options we are asking the
>> distribution installer to perform magic. Moving as much of this logic
>> into a normal init script for better maintenance is desirable.
>
> Not (necessarily) the installer but the program that configures kdump.
> system-config-kdump on Red Hat, YaST on SUSE.
Right. Somehow I thought YaST was the installer my mistake.
>> Bernhard does that sound useful to you?
>
> I don't see any problems. I don't know how much effort is it to free
> already reserved crashkernel memory, but I guess it's not really
> complicated.
Right.
> Maybe that "1/32" should be specified on the command line like
>
>
> crashkernel=>>5
>
> (for 1/32*system_memory == system_memory>>5), OTOH I have no real strong
> opinion.
The idea is for the system to give us as much as it can stand and
userspace gives the rest back. The maximum memory any particular
kernel can stand to give up is a tractable kernel level problem, and
we can make it autotune like any other kernel tunable. What a crash
kernel needs totally depends on the implementation.
Eric
next prev parent reply other threads:[~2009-08-07 22:16 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 11:19 [Patch 0/7] Implement crashkernel=auto Amerigo Wang
2009-08-05 11:19 ` [Patch 1/7] x86: add CONFIG_KEXEC_AUTO_RESERVE Amerigo Wang
2009-08-05 13:41 ` Neil Horman
2009-08-05 14:45 ` Andi Kleen
2009-08-05 20:07 ` Eric W. Biederman
2009-08-06 1:55 ` Amerigo Wang
2009-08-06 7:15 ` Andi Kleen
2009-08-06 7:44 ` Amerigo Wang
2009-08-06 7:56 ` Amerigo Wang
2009-08-05 11:19 ` [Patch 2/7] x86: implement crashkernel=auto Amerigo Wang
2009-08-05 13:43 ` Neil Horman
2009-08-06 1:45 ` Amerigo Wang
2009-08-05 22:51 ` Yu, Fenghua
2009-08-06 1:56 ` Amerigo Wang
2009-08-05 11:19 ` [Patch 3/7] ia64: add CONFIG_KEXEC_AUTO_RESERVE Amerigo Wang
2009-08-05 13:49 ` Neil Horman
2009-08-05 11:19 ` [Patch 4/7] ia64: implement crashkernel=auto Amerigo Wang
2009-08-05 13:46 ` Neil Horman
2009-08-05 11:19 ` [Patch 5/7] powerpc: add CONFIG_KEXEC_AUTO_RESERVE Amerigo Wang
2009-08-05 13:49 ` Neil Horman
2009-08-05 11:20 ` [Patch 6/7] powerpc: implement crashkernel=auto Amerigo Wang
2009-08-05 13:50 ` Neil Horman
2009-08-05 11:20 ` [Patch 7/7] doc: update the kdump document Amerigo Wang
2009-08-05 13:33 ` [Patch 0/7] Implement crashkernel=auto Eric W. Biederman
2009-08-05 14:04 ` Neil Horman
2009-08-05 22:57 ` Eric W. Biederman
2009-08-06 2:05 ` Amerigo Wang
2009-08-06 2:47 ` Eric W. Biederman
2009-08-06 3:39 ` Amerigo Wang
2009-08-06 3:51 ` Eric W. Biederman
2009-08-06 5:57 ` Amerigo Wang
2009-08-06 6:14 ` Eric W. Biederman
2009-08-06 6:37 ` Amerigo Wang
2009-08-06 8:35 ` Eric W. Biederman
2009-08-06 8:47 ` Eric W. Biederman
2009-08-06 9:04 ` Amerigo Wang
2009-08-07 19:13 ` Bernhard Walle
2009-08-06 9:11 ` Amerigo Wang
2009-08-07 19:50 ` Eric W. Biederman
2009-08-07 21:03 ` Andi Kleen
2009-08-07 21:26 ` Bernhard Walle
2009-08-07 22:06 ` Eric W. Biederman
2009-08-07 21:31 ` Bernhard Walle
2009-08-07 22:16 ` Eric W. Biederman [this message]
2009-08-10 3:11 ` Amerigo Wang
2009-08-06 1:39 ` Amerigo Wang
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=m1tz0jmfqs.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=andi@firstfloor.org \
--cc=avorontsov@ru.mvista.com \
--cc=bernhard.walle@gmx.de \
--cc=kexec@lists.infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nhorman@redhat.com \
--cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox