From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: x86 swiotlb questions Date: Fri, 15 Dec 2006 13:53:03 +0000 Message-ID: <4582B6CF.76E4.0078.0@novell.com> References: <4582A833.76E4.0078.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com, Keir Fraser List-Id: xen-devel@lists.xenproject.org >> - 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