From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
Alex Williams <awilliams@iweb.com>
Subject: Re: Possible regression: XEN 4.0.0 total_memory decrease
Date: Mon, 19 Apr 2010 08:51:59 +0100 [thread overview]
Message-ID: <C7F1CA2F.11B1E%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4BCC23F9020000780003AC6D@vpn.id2.novell.com>
On 19/04/2010 08:35, "Jan Beulich" <JBeulich@novell.com> wrote:
>> boot_e820 has chunks cut out of it for stashing kexec stuff, as well as all
>> the multiboot modules. The value thereby obtained is just confusing to users
>> who think we've binned possibly 100s of megabytes (if they run a big
>> initrd).
>
> The piece cut off for kexec imo shouldn't be counted as (usable)
> system RAM; the piece for the multiboot modules certainly should,
> but perhaps it would then be better to account for that explicitly
> instead of reporting a possibly much higher value than is actually
> available at runtime?
I think it's quite open to debate what should be included in total_memory.
Certainly I think kexec can be, as why is it different from any other in-use
memory in the system in that regard?
-- Keir
next prev parent reply other threads:[~2010-04-19 7:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 15:54 Possible regression: XEN 4.0.0 total_memory decrease Alex Williams
2010-04-15 16:33 ` Keir Fraser
2010-04-15 17:33 ` Alex Williams
2010-04-15 17:42 ` Alex Williams
2010-04-15 18:05 ` Keir Fraser
2010-04-15 18:23 ` Keir Fraser
2010-04-16 7:53 ` Jan Beulich
2010-04-16 17:37 ` Keir Fraser
2010-04-19 7:35 ` Jan Beulich
2010-04-19 7:51 ` Keir Fraser [this message]
2010-04-15 18:26 ` Alex Williams
2010-04-15 18:34 ` Keir Fraser
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=C7F1CA2F.11B1E%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=JBeulich@novell.com \
--cc=Xen-devel@lists.xensource.com \
--cc=awilliams@iweb.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;
as well as URLs for NNTP newsgroup(s).