WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Possible regression: XEN 4.0.0 total_memory decrease

To: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] Possible regression: XEN 4.0.0 total_memory decrease
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Mon, 19 Apr 2010 08:51:59 +0100
Cc: "Xen-devel@xxxxxxxxxxxxxxxxxxx" <Xen-devel@xxxxxxxxxxxxxxxxxxx>, Alex Williams <awilliams@xxxxxxxx>
Delivery-date: Mon, 19 Apr 2010 00:53:35 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4BCC23F9020000780003AC6D@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcrfkvJ+yBj6OudnSOCBn+StZ/U6JAAAj3/A
Thread-topic: [Xen-devel] Possible regression: XEN 4.0.0 total_memory decrease
User-agent: Microsoft-Entourage/12.24.0.100205
On 19/04/2010 08:35, "Jan Beulich" <JBeulich@xxxxxxxxxx> 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



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel