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/
Home Products Support Community News


Re: [Xen-devel] Assigning contiguous memory to a driver domain

To: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] Assigning contiguous memory to a driver domain
From: Goswin von Brederlow <goswin-v-b@xxxxxx>
Date: Wed, 15 Sep 2010 13:58:30 +0200
Cc: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Rafal Wojtczuk <rafal@xxxxxxxxxxxxxxxxxxxxxx>, Joanna Rutkowska <joanna@xxxxxxxxxxxxxxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Wed, 15 Sep 2010 05:00:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C90CF39020000780001647E@xxxxxxxxxxxxxxxxxx> (Jan Beulich's message of "Wed, 15 Sep 2010 12:50:49 +0100")
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: <20100914092439.GA1000@email> <4C8F5E580200007800015F71@xxxxxxxxxxxxxxxxxx> <20100915090842.GB1583@email> <20100915093910.GC1583@email> <4C90B31902000078000163E8@xxxxxxxxxxxxxxxxxx> <4C90A32A.7010803@xxxxxxxxxxxxxxxxxxxxxx> <4C90C3200200007800016442@xxxxxxxxxxxxxxxxxx> <4C90A8E4.9090004@xxxxxxxxxxxxxxxxxxxxxx> <4C90CF39020000780001647E@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.110009 (No Gnus v0.9) XEmacs/21.4.22 (linux, no MULE)
"Jan Beulich" <JBeulich@xxxxxxxxxx> writes:

>> Well, we do have 2 driver domains in Qubes: one is the netvm (NIC
>> drivers), and the other one is Dom0 (storage, video, etc). BTW, how is
>> it that the drivers in Dom0 never has this problem with allocating
>> continues memory (even if we keep xen free memory = 0)?
> Merely because post-boot there would not usually be allocations.

It is also called fragmentation.

dom0 gets its memory at the start and probably all in one big
chunk. Other domains have to use the bits and pices that happen to be
free when the domain is started.


Xen-devel mailing list

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