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][PATCH] 0/9 Populate-on-demand memory

To: "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx>
Subject: Re: [Xen-devel] [RFC][PATCH] 0/9 Populate-on-demand memory
From: "George Dunlap" <George.Dunlap@xxxxxxxxxxxxx>
Date: Wed, 24 Dec 2008 15:46:00 +0000
Cc: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 24 Dec 2008 07:46:25 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=9I18i/Ulig/eiM6pw6fJBcLMtQHL7VQuI75dlq60mEc=; b=OFwdc1LGttQvLHiU2R3m8dVSUD1K3AjHqqfKQhSz9DQBOIKU78UroYI73KHna2tm+R 74mWMqbmLQmIqClDv47gSqBWhEiyktrvG2MwNVWwHr++o9LWUzYkcud47U/pE7tOPlBO z3nYMD3GvF7ZVSNfxLFLAZwZ3KbaM7aTyierE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=CWKSNq9eN9KgaHnMSyUd9uuKDEtzDXFKExP/uNKLaV7qquUgxr8tOumUUq179DkPw9 noRBamq0X+JfZsp1NZG8ciJUnyAYQwJMoKPm9Xrct5pB8suZbWUbh+egg47s3LNx+kD1 9opGg/KORf76bYIKSDpM3UgMbwvTap2Y05ifA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <30c85335-4729-4ae4-bb24-0c9dc2abe3cf@default>
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>
References: <de76405a0812240642i42f9c1f2ud7ca7d9d1bf4e400@xxxxxxxxxxxxxx> <30c85335-4729-4ae4-bb24-0c9dc2abe3cf@default>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, Dec 24, 2008 at 3:35 PM, Dan Magenheimer
<dan.magenheimer@xxxxxxxxxx> wrote:
>> We could to allocate a new page at that point; but it's likely that
>> the allocation will fail unless there happens to be memory lying
>> around somewhere, not used by dom0 or any other doamin.  And if that
>> were the case, why not just start it with that much memory to begin
>> with?
>
> Actually, if dom0_mem is used rather than the default of letting
> domain0 absorb all free memory and dole it as needed to launching
> VMs, there will almost always be some memory lying around.

At any rate, I suppose it might not be a bad idea to *try* to allocate
more memory in an emergency.  I'll add that to the list of
improvements.

 -George

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