From: Vivek Goyal <vgoyal@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: jerry.hoemann@hp.com, rob@landley.net, tglx@linutronix.de,
mingo@redhat.com, x86@kernel.org, matt.fleming@intel.com,
yinghai@kernel.org, penberg@kernel.org,
akpm@linux-foundation.org, linux-doc@vger.kernel.org,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Early use of boot service memory
Date: Thu, 14 Nov 2013 10:26:23 -0500 [thread overview]
Message-ID: <20131114152623.GC3913@redhat.com> (raw)
In-Reply-To: <52840206.5020006@zytor.com>
On Wed, Nov 13, 2013 at 02:49:42PM -0800, H. Peter Anvin wrote:
[..]
> In other words, allocating the crashkernel high has ALL the advantages,
> plus a few more, and NONE of the disadvantages.
It allocates low memory for swiotlb. So that extra 72M allocation is the
disadvantage. With so many virtual machines on a single host, I don't
want to reserve extra 72MB on each virtual machine while I could
easily do away with memory reservation below 4G.
So I do think that first trying memory below 896M, then below 4G and then
above 4G makes sense and we should modify crashkernel=X to handle that.
Thanks
Vivek
prev parent reply other threads:[~2013-11-14 15:26 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 2:15 [PATCH 0/3] Early use of boot service memory Jerry Hoemann
2013-11-12 2:15 ` [PATCH 1/3] efi: " Jerry Hoemann
2013-11-12 2:15 ` [PATCH 2/3] x86: avoid efi_reserve_boot_services Jerry Hoemann
2013-11-12 2:15 ` [PATCH 3/3] x86, efi: Early use of boot service memory Jerry Hoemann
2013-11-12 10:37 ` [PATCH 0/3] " Pekka Enberg
2013-11-12 17:55 ` jerry.hoemann
2013-11-12 18:48 ` Pekka Enberg
2013-11-12 21:52 ` jerry.hoemann
2013-11-12 18:58 ` H. Peter Anvin
2013-11-13 22:45 ` jerry.hoemann
2013-11-13 22:49 ` H. Peter Anvin
2013-11-13 23:57 ` jerry.hoemann
2013-11-14 0:05 ` H. Peter Anvin
2013-11-14 1:40 ` jerry.hoemann
2014-08-01 9:54 ` Yuhong Bao
2013-11-14 8:24 ` Pekka Enberg
2013-11-14 18:04 ` jerry.hoemann
2013-11-14 18:44 ` Pekka Enberg
2013-11-14 18:45 ` H. Peter Anvin
2013-11-15 0:50 ` jerry.hoemann
2013-11-15 6:24 ` Ingo Molnar
2013-11-15 6:55 ` Yinghai Lu
2013-11-15 6:59 ` H. Peter Anvin
2013-11-15 14:07 ` Vivek Goyal
2013-11-15 17:33 ` Yinghai Lu
2013-11-15 17:40 ` H. Peter Anvin
2013-11-15 18:30 ` Vivek Goyal
2013-11-15 18:46 ` H. Peter Anvin
2013-11-15 19:16 ` H. Peter Anvin
2013-11-18 15:22 ` Vivek Goyal
2013-11-18 18:29 ` H. Peter Anvin
2013-11-18 18:52 ` Vivek Goyal
2013-11-19 1:32 ` H. Peter Anvin
2013-11-19 3:02 ` Yinghai Lu
2013-11-15 18:03 ` Vivek Goyal
2013-11-15 22:24 ` Yinghai Lu
2013-11-15 22:55 ` jerry.hoemann
2013-11-15 23:43 ` Yinghai Lu
2013-11-18 15:32 ` Vivek Goyal
2013-11-18 19:34 ` Yinghai Lu
2013-11-18 19:39 ` Vivek Goyal
2013-11-15 18:16 ` jerry.hoemann
2013-11-15 19:13 ` jerry.hoemann
2013-11-18 15:42 ` Vivek Goyal
2013-11-15 8:36 ` Pekka Enberg
2013-11-14 15:26 ` Vivek Goyal [this message]
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=20131114152623.GC3913@redhat.com \
--to=vgoyal@redhat.com \
--cc=akpm@linux-foundation.org \
--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@redhat.com \
--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).