From: Vivek Goyal <vgoyal@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
jerry.hoemann@hp.com, Matthew Garrett <mjg59@srcf.ucam.org>,
Rob Landley <rob@landley.net>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
the arch/x86 maintainers <x86@kernel.org>,
Matt Fleming <matt.fleming@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Borislav Petkov <bp@suse.de>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-efi@vger.kernel.org, Pekka Enberg <penberg@kernel.org>,
Ingo Molnar <mingo.kernel.org@gmail.com>
Subject: Re: [RFC v2 0/2] Early use of boot service memory
Date: Thu, 21 Nov 2013 21:34:06 -0500 [thread overview]
Message-ID: <20131122023406.GG31921@redhat.com> (raw)
In-Reply-To: <528EB40A.3040203@zytor.com>
On Thu, Nov 21, 2013 at 05:31:54PM -0800, H. Peter Anvin wrote:
> On 11/21/2013 05:29 PM, Yinghai Lu wrote:
> > On Thu, Nov 21, 2013 at 5:25 PM, <jerry.hoemann@hp.com> wrote:
> >> On Thu, Nov 21, 2013 at 05:12:57PM -0800, H. Peter Anvin wrote:
> >>
> >> Large systems w/ lots of IO require large crash kernel allocations for
> >> the kernel to boot. Then you have to worry about the OOM killer.....
> >
> > so go with crashkernel=1024M,high.
> >
>
> Yes, there is no bloody excuse to hog that much low memory.
Curious, why is low memory precious on x86_64? Who is going to use it?
Thanks
Vivek
next prev parent reply other threads:[~2013-11-22 2:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 21:01 [RFC v2 0/2] Early use of boot service memory Jerry Hoemann
2013-11-21 21:01 ` [RFC v2 1/2] efi: " Jerry Hoemann
2013-11-21 21:01 ` [RFC v2 2/2] x86, " Jerry Hoemann
2013-11-21 22:19 ` Borislav Petkov
[not found] ` <1385067686-73500-1-git-send-email-jerry.hoemann-VXdhtT5mjnY@public.gmane.org>
2013-11-21 23:07 ` [RFC v2 0/2] " Matthew Garrett
[not found] ` <20131121230744.GA31592-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-11-21 23:18 ` H. Peter Anvin
2013-11-21 23:37 ` Matthew Garrett
2013-11-22 1:12 ` H. Peter Anvin
2013-11-22 1:25 ` jerry.hoemann
[not found] ` <20131122012524.GA5627-dMAi7lA+vBPDUbYHzcRnttBPR1lH4CV8@public.gmane.org>
2013-11-22 1:29 ` Yinghai Lu
2013-11-22 2:29 ` Vivek Goyal
[not found] ` <20131122022957.GE31921-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-11-22 3:32 ` HATAYAMA Daisuke
[not found] ` <CAE9FiQUx5rnA0kpqXRQYtpj9Qk-4bPGaUKEbbF=XHsZbnSd6Rg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-22 1:31 ` H. Peter Anvin
2013-11-22 2:34 ` Vivek Goyal [this message]
[not found] ` <20131122023406.GG31921-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-11-22 2:42 ` H. Peter Anvin
2013-11-22 2:32 ` Vivek Goyal
2013-11-21 23:31 ` jerry.hoemann-VXdhtT5mjnY
2013-11-21 23:38 ` Matthew Garrett
[not found] ` <20131121233831.GB32121-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-11-22 1:05 ` jerry.hoemann-VXdhtT5mjnY
2013-11-22 1:16 ` Matthew Garrett
2013-12-16 18:43 ` jerry.hoemann
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=20131122023406.GG31921@redhat.com \
--to=vgoyal@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=jerry.hoemann@hp.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo.kernel.org@gmail.com \
--cc=mingo@redhat.com \
--cc=mjg59@srcf.ucam.org \
--cc=penberg@kernel.org \
--cc=rob@landley.net \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).