xen-devel
[Xen-devel] RE: Tmem vs order>0 allocation, workaround RFC
To: |
Jan Beulich <JBeulich@xxxxxxxxxx> |
Subject: |
[Xen-devel] RE: Tmem vs order>0 allocation, workaround RFC |
From: |
Dan Magenheimer <dan.magenheimer@xxxxxxxxxx> |
Date: |
Tue, 16 Feb 2010 07:31:58 -0800 (PST) |
Cc: |
xen-devel@xxxxxxxxxxxxxxxxxxx, George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, kurt.hackel@xxxxxxxxxx, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, TimDeegan <Tim.Deegan@xxxxxxxxxxxxx>, Patrick Colp <pjcolp@xxxxxxxxx>, Grzegorz Milos <gm281@xxxxxxxxx>, Keir, Fraser <keir.fraser@xxxxxxxxxxxxx>, AndrewPeace <Andrew.Peace@xxxxxxxxxxxxx> |
Delivery-date: |
Tue, 16 Feb 2010 07:33:58 -0800 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<4B7AC4AD020000780002FA3D@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> |
References: |
<2af13319-6b44-44e2-ab62-a0615208cf64@default> <C79F1B58.A196%keir.fraser@xxxxxxxxxxxxx> <78c49794-4454-4c3b-80a6-72efcbc73fb3@default><78c49794-4454-4c3b-80a6-72efcbc73fb3@default> <057c0f45-9c97-4b8a-8efa-1726fd951e19@default> <4B7A6363020000780002F93C@xxxxxxxxxxxxxxxxxx><4B7A6363020000780002F93C@xxxxxxxxxxxxxxxxxx> <d2556e50-476d-487d-8fa8-aae67f63396c@default 4B7AC4AD020000780002FA3D@xxxxxxxxxxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
> From: Jan Beulich [mailto:JBeulich@xxxxxxxxxx]
> Subject: RE: Tmem vs order>0 allocation, workaround RFC
>
> >>> Dan Magenheimer <dan.magenheimer@xxxxxxxxxx> 16.02.10 16:05 >>>
> >Under what circumstances does dom0 require single-page-below-4G
> >allocations? Is it only for bounce buffers for PCI passthrough
> >of old devices with 32-bit addressing limitations? Or am I
> >missing a much more common case?
>
> Not just for pass-through; all devices only supporting 32-bit
> addressing would have such requirements, and particularly common
> ones are display adapters which have DRM/AGP drivers loaded for
> them.
Right, but those are statically allocated when dom0 is
launched, not dynamically allocated later after tmem
(or other memory allocation technologies) begin working,
right? Whereas pass-through devices would need below-4G
pages later?
(And 32-bit devices in a 1TB machine seems a bit of a
stretch, but I suppose it is good to enumerate all the
cases.)
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- RE: [Xen-devel] Tmem vs order>0 allocation, workaround RFC, (continued)
- RE: [Xen-devel] Tmem vs order>0 allocation, workaround RFC, Dan Magenheimer
- [Xen-devel] Re: Tmem vs order>0 allocation, workaround RFC, Keir Fraser
- [Xen-devel] RE: Tmem vs order>0 allocation, workaround RFC, Dan Magenheimer
- [Xen-devel] Re: Tmem vs order>0 allocation, workaround RFC, Keir Fraser
- [Xen-devel] RE: Tmem vs order>0 allocation, workaround RFC, Dan Magenheimer
- [Xen-devel] Re: Tmem vs order>0 allocation, workaround RFC, Keir Fraser
- [Xen-devel] RE: Tmem vs order>0 allocation, workaround RFC, Dan Magenheimer
- [Xen-devel] RE: Tmem vs order>0 allocation, workaround RFC, Jan Beulich
- [Xen-devel] RE: Tmem vs order>0 allocation, workaround RFC, Dan Magenheimer
- [Xen-devel] RE: Tmem vs order>0 allocation, workaround RFC, Jan Beulich
- [Xen-devel] RE: Tmem vs order>0 allocation, workaround RFC,
Dan Magenheimer <=
- [Xen-devel] RE: Tmem vs order>0 allocation, workaround RFC, Jan Beulich
- [Xen-devel] RE: Tmem vs order>0 allocation, workaround RFC, Dan Magenheimer
- Re: [Xen-devel] RE: Tmem vs order>0 allocation, workaround RFC, Konrad Rzeszutek Wilk
|
|
|