public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Bernhard Walle <bernhard.walle@gmx.de>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Neil Horman <nhorman@redhat.com>,
	tony.luck@intel.com, linux-ia64@vger.kernel.org,
	Amerigo Wang <amwang@redhat.com>,
	Kexec Mailing List <kexec@lists.infradead.org>,
	linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
	akpm@linux-foundation.org,
	Anton Vorontsov <avorontsov@ru.mvista.com>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: [Patch 0/7] Implement crashkernel=auto
Date: Fri, 07 Aug 2009 23:31:52 +0200	[thread overview]
Message-ID: <4A7C9D48.3030405@gmx.de> (raw)
In-Reply-To: <m1iqgze740.fsf@fess.ebiederm.org>

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.

> 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. 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.


Regards,
Bernhard

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

  parent reply	other threads:[~2009-08-07 21:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090805112123.6552.73574.sendpatchset@localhost.localdomain>
     [not found] ` <m1eirqtmey.fsf@fess.ebiederm.org>
     [not found]   ` <20090805140408.GJ7259@hmsreliant.think-freely.org>
     [not found]     ` <m1skg5vpgg.fsf@fess.ebiederm.org>
     [not found]       ` <4A7A3A78.7080200@redhat.com>
     [not found]         ` <m1y6pxr737.fsf@fess.ebiederm.org>
     [not found]           ` <4A7A506B.2060008@redhat.com>
     [not found]             ` <m1ljlxsiox.fsf@fess.ebiederm.org>
     [not found]               ` <4A7A70E5.2010204@redhat.com>
     [not found]                 ` <m1bpmtqxjh.fsf@fess.ebiederm.org>
     [not found]                   ` <4A7A7A0F.6070906@redhat.com>
     [not found]                     ` <m1iqh1nxv3.fsf@fess.ebiederm.org>
     [not found]                       ` <4A7A9E54.60705@redhat.com>
2009-08-07 19:50                         ` [Patch 0/7] Implement crashkernel=auto 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 [this message]
2009-08-07 22:16                             ` Eric W. Biederman
2009-08-10  3:11                           ` 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=4A7C9D48.3030405@gmx.de \
    --to=bernhard.walle@gmx.de \
    --cc=akpm@linux-foundation.org \
    --cc=amwang@redhat.com \
    --cc=andi@firstfloor.org \
    --cc=avorontsov@ru.mvista.com \
    --cc=ebiederm@xmission.com \
    --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