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] x86 swiotlb questions

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>,"Keir Fraser" <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] x86 swiotlb questions
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Fri, 15 Dec 2006 13:53:03 +0000
Delivery-date: Fri, 15 Dec 2006 05:52:23 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C1A8553B.623F%keir@xxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4582A833.76E4.0078.0@xxxxxxxxxx> <C1A8553B.623F%keir@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>> - The DMA bit widths can be set to different values in Xen and kernel, which
>> can
>> lead to surprising results, I would think. Shouldn't the kernel rather obtain
>> Xen's
>> value, so they are consistent?
>
>We would like to generalise Xen's heap allocator so that it keeps separate
>heaps for different bit widths. Then there would be no 'DMA width' or 'DMA
>pool' in Xen.

I already have patches ready to do this (the DMA thing really is a nice side
effect, I mostly wanted it for 32on64, so that I can restrict domain
allocations for 32-bit domains). Are you saying I should throw away the
DMA specialization then altogether (I already have no special DMA heap
anymore)? The leftovers from it are so that one can reserve some portion
of low memory to be returned only when the width restriction is low enough
(i.e. to retain dma_emergency_pool functionality), which certainly isn't
really appropriate anymore now (it should rather be a percentage or
something like that, so that the lower you get the more of the memory
remains reserved for specialized allocations).

Jan

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