From: Petr Tesarik <ptesarik@suse.cz> To: Dave Young <dyoung@redhat.com> Cc: dzickus@redhat.com, Neil Horman <nhorman@redhat.com>, Tony Luck <tony.luck@intel.com>, bhe@redhat.com, Michael Ellerman <mpe@ellerman.id.au>, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, Martin Schwidefsky <schwidefsky@de.ibm.com>, "Eric W. Biederman" <ebiederm@xmission.com>, Benjamin Herrenschmidt <benh@kernel.crashing.org>, Hari Bathini <hbathini@linux.vnet.ibm.com>, Cong Wang <xiyou.wangcong@gmail.com>, Andrew Morton <akpm@linux-foundation.org>, Ingo Molnar <mingo@kernel.org>, Vivek Goyal <vgoyal@redhat.com> Subject: Re: [PATCH] kdump: add default crashkernel reserve kernel config options Date: Thu, 24 May 2018 11:02:41 +0200 [thread overview] Message-ID: <20180524110241.3f60997c@ezekiel.suse.cz> (raw) In-Reply-To: <20180524072627.GA1940@dhcp-128-65.nay.redhat.com> On Thu, 24 May 2018 15:26:27 +0800 Dave Young <dyoung@redhat.com> wrote: > On 05/24/18 at 08:57am, Petr Tesarik wrote: >[...] > > What is "a very minimal initrd"? Last time I had to make a significant > > adjustment to the estimation for openSUSE, this was caused by growing > > user-space requirements (systemd in this case, but I don't want to > > start flamewars on that topic, please). > > Still I think we have agreement and same feeling about the userspace > memory requirement. I think although it is hard, we have been still > trying to shrink the initramfs memory use. > > Besides of distribution use, why people can not use some minimal > initrd? For example only a basic shell and some necessary tools and > basic storage eg. raw disks supported, and he/she can just collect the > panic infomation by himself in a shell. Again, I'm having trouble with the definition of a "minimal initrd" and also with the definition of a "workstation". I have already seen a sad case where kdump started going OOM after connecting a 4K monitor, because, well, it needed a bigger framebuffer... OTOH you wrote in another mail that RH has tested some values on a variety of hardware, so you seem to have a clue. Good for you. I still believe it is moving policy into the kernel. Based on past experience, I expect that certain users will argue that "crashkernel=auto" should work out of the box on their HPE Superdome with 600+ LUNs attached... As you wrote elsewhere in the thread: > I means this patch is not trying to force add a fixed value for crashkernel > in kernel code. It provides another way one can use on kernel build time > the value just works. I don't mind if it is added, although I don't find it very useful. Petr T
WARNING: multiple messages have this Message-ID (diff)
From: Petr Tesarik <ptesarik@suse.cz> To: Dave Young <dyoung@redhat.com> Cc: dzickus@redhat.com, Neil Horman <nhorman@redhat.com>, Tony Luck <tony.luck@intel.com>, bhe@redhat.com, Michael Ellerman <mpe@ellerman.id.au>, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, Hari Bathini <hbathini@linux.vnet.ibm.com>, "Eric W. Biederman" <ebiederm@xmission.com>, Benjamin Herrenschmidt <benh@kernel.crashing.org>, Martin Schwidefsky <schwidefsky@de.ibm.com>, Cong Wang <xiyou.wangcong@gmail.com>, Andrew Morton <akpm@linux-foundation.org>, Ingo Molnar <mingo@kernel.org>, Vivek Goyal <vgoyal@redhat.com> Subject: Re: [PATCH] kdump: add default crashkernel reserve kernel config options Date: Thu, 24 May 2018 11:02:41 +0200 [thread overview] Message-ID: <20180524110241.3f60997c@ezekiel.suse.cz> (raw) In-Reply-To: <20180524072627.GA1940@dhcp-128-65.nay.redhat.com> On Thu, 24 May 2018 15:26:27 +0800 Dave Young <dyoung@redhat.com> wrote: > On 05/24/18 at 08:57am, Petr Tesarik wrote: >[...] > > What is "a very minimal initrd"? Last time I had to make a significant > > adjustment to the estimation for openSUSE, this was caused by growing > > user-space requirements (systemd in this case, but I don't want to > > start flamewars on that topic, please). > > Still I think we have agreement and same feeling about the userspace > memory requirement. I think although it is hard, we have been still > trying to shrink the initramfs memory use. > > Besides of distribution use, why people can not use some minimal > initrd? For example only a basic shell and some necessary tools and > basic storage eg. raw disks supported, and he/she can just collect the > panic infomation by himself in a shell. Again, I'm having trouble with the definition of a "minimal initrd" and also with the definition of a "workstation". I have already seen a sad case where kdump started going OOM after connecting a 4K monitor, because, well, it needed a bigger framebuffer... OTOH you wrote in another mail that RH has tested some values on a variety of hardware, so you seem to have a clue. Good for you. I still believe it is moving policy into the kernel. Based on past experience, I expect that certain users will argue that "crashkernel=auto" should work out of the box on their HPE Superdome with 600+ LUNs attached... As you wrote elsewhere in the thread: > I means this patch is not trying to force add a fixed value for crashkernel > in kernel code. It provides another way one can use on kernel build time > the value just works. I don't mind if it is added, although I don't find it very useful. Petr T _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2018-05-24 9:02 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-21 2:53 [PATCH] kdump: add default crashkernel reserve kernel config options Dave Young 2018-05-21 2:53 ` Dave Young 2018-05-21 19:02 ` Andrew Morton 2018-05-21 19:02 ` Andrew Morton 2018-05-22 1:43 ` Dave Young 2018-05-22 1:43 ` Dave Young 2018-05-22 1:48 ` Dave Young 2018-05-22 1:48 ` Dave Young 2018-05-23 7:06 ` Dave Young 2018-05-23 7:06 ` Dave Young 2018-05-23 15:53 ` Eric W. Biederman 2018-05-23 15:53 ` Eric W. Biederman 2018-05-23 20:22 ` Petr Tesarik 2018-05-23 20:22 ` Petr Tesarik 2018-05-24 1:49 ` Dave Young 2018-05-24 1:49 ` Dave Young 2018-05-24 6:57 ` Petr Tesarik 2018-05-24 6:57 ` Petr Tesarik 2018-05-24 7:26 ` Dave Young 2018-05-24 7:26 ` Dave Young 2018-05-24 7:39 ` Dave Young 2018-05-24 7:39 ` Dave Young 2018-05-24 7:56 ` Dave Young 2018-05-24 7:56 ` Dave Young 2018-05-24 8:29 ` Baoquan He 2018-05-24 8:29 ` Baoquan He 2018-05-24 9:02 ` Petr Tesarik [this message] 2018-05-24 9:02 ` Petr Tesarik 2018-05-24 7:31 ` Baoquan He 2018-05-24 7:31 ` Baoquan He 2018-05-24 16:34 ` Eric W. Biederman 2018-05-24 16:34 ` Eric W. Biederman 2018-05-25 4:59 ` Petr Tesarik 2018-05-25 4:59 ` Petr Tesarik 2018-05-25 20:00 ` Eric W. Biederman 2018-05-25 20:00 ` Eric W. Biederman 2018-05-28 12:34 ` Petr Tesarik 2018-05-28 12:34 ` Petr Tesarik 2018-05-29 12:19 ` Eric W. Biederman 2018-05-29 12:19 ` Eric W. Biederman 2018-05-24 1:42 ` Dave Young 2018-05-24 1:42 ` Dave Young 2018-05-24 16:41 ` Eric W. Biederman 2018-05-24 16:41 ` Eric W. Biederman 2018-05-25 2:43 ` Dave Young 2018-05-25 2:43 ` Dave Young
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=20180524110241.3f60997c@ezekiel.suse.cz \ --to=ptesarik@suse.cz \ --cc=akpm@linux-foundation.org \ --cc=benh@kernel.crashing.org \ --cc=bhe@redhat.com \ --cc=dyoung@redhat.com \ --cc=dzickus@redhat.com \ --cc=ebiederm@xmission.com \ --cc=hbathini@linux.vnet.ibm.com \ --cc=kexec@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@kernel.org \ --cc=mpe@ellerman.id.au \ --cc=nhorman@redhat.com \ --cc=schwidefsky@de.ibm.com \ --cc=tony.luck@intel.com \ --cc=vgoyal@redhat.com \ --cc=xiyou.wangcong@gmail.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.