From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernhard Walle Date: Fri, 07 Aug 2009 21:31:52 +0000 Subject: Re: [Patch 0/7] Implement crashkernel=auto Message-Id: <4A7C9D48.3030405@gmx.de> List-Id: References: <20090805112123.6552.73574.sendpatchset@localhost.localdomain> <20090805140408.GJ7259@hmsreliant.think-freely.org> <4A7A3A78.7080200@redhat.com> <4A7A506B.2060008@redhat.com> <4A7A70E5.2010204@redhat.com> <4A7A7A0F.6070906@redhat.com> <4A7A9E54.60705@redhat.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: "Eric W. Biederman" Cc: Amerigo Wang , Neil Horman , linux-kernel@vger.kernel.org, tony.luck@intel.com, linux-ia64@vger.kernel.org, akpm@linux-foundation.org, Ingo Molnar , Anton Vorontsov , Andi Kleen , Kexec Mailing List 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