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] [RFC] new totalmem= boot parameter

To: Sarina Canelake <sarina.canelake@xxxxxxxxxx>
Subject: Re: [Xen-devel] [RFC] new totalmem= boot parameter
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 21 Jul 2010 08:46:11 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 21 Jul 2010 00:47:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100720212616.GB15056@xxxxxxxxxxxxxxxxxxxxxxxx>
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: AcsoUms0pmfgQCRpRPiThAq7FzRfbQAVl5Ek
Thread-topic: [Xen-devel] [RFC] new totalmem= boot parameter
User-agent: Microsoft-Entourage/12.24.0.100205
On 20/07/2010 22:26, "Sarina Canelake" <sarina.canelake@xxxxxxxxxx> wrote:

>> It doesn't sound *very* useful. But then neither is mem= really. We can add
>> something like this if you really need it. So what's the motivation?
>> 
> 
> I found it useful while I was testing various core dumping capabilities.
> Using a boot-time argument to limit memory eliminates the need for pulling
> out DIMMs (which I couldn't do anyways, as the machines I was working
> on are remote). However mem= didn't suffice for this purpose
> beyond 3 Gb since, as I mentioned, it limits the physical address
> rather than the amount of RAM, which is what I thought it was
> supposed to do. Hence the implementation of totalmem=, which made my
> 16Gb+ boxes capable of imitating various, specific smaller configurations.

Okay, I applied a reimplemented form of your patch as xen-unstable:21837.
The option is named availmem rather than totalmem. I think it's a slightly
better name.

 -- Keir

> Alternatively, if mem= isn't used very frequently, perhaps it wouldn't
> be a bad idea to simply update the functionality of mem= to limit the
> total memory rather than the physical address.



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

<Prev in Thread] Current Thread [Next in Thread>