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] USB virt status --- Help please!!!

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] USB virt status --- Help please!!!
From: Muli Ben-Yehuda <mulix@xxxxxxxxx>
Date: Tue, 15 Nov 2005 21:14:32 +0200
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, harry <harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, sanjay.kushwaha@xxxxxxxxx, mark.williamson@xxxxxxxxxxxx
Delivery-date: Tue, 15 Nov 2005 19:15:05 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <f6002ab13acb887aca3ccae8a535a6c9@xxxxxxxxxxxx>
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: <A95E2296287EAD4EB592B5DEEFCE0E9D32E930@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <1131906498.7898.20.camel@localhost> <aa8e1dea0e3038d0d50d615fe9049458@xxxxxxxxxxxx> <1131963126.28635.3.camel@xxxxxxxxxxxxxxxxxxxxx> <4b44eaf35c9bb921b7940c157936c38a@xxxxxxxxxxxx> <1131989401.3989.19.camel@xxxxxxxxxxxxxxxxxxxxx> <681ca7ec21d7aac712bae9e9cde2c493@xxxxxxxxxxxx> <1131994239.3989.41.camel@xxxxxxxxxxxxxxxxxxxxx> <20051114214609.GC24964@xxxxxxxxxxxxxxxxxxx> <f6002ab13acb887aca3ccae8a535a6c9@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.11
On Tue, Nov 15, 2005 at 10:23:40AM +0000, Keir Fraser wrote:

> Not expensive in time, but it does waste memory if it's unused.
> Currently we allocate a 64MB aperture if the machine has memory mapped 
> above 2GB (this catches devices like aacraid that can only address 31 
> bits). I could also allocate an aperture of, say, 2MB for smaller 
> systems. There is of course a tension between not wasting memory yet 
> having a big enough aperture that the system will not run out of iommu 
> space and crash even when stressed.

Since Andi's ZONE_DMA32 patches went in last night, how about
foregoing the up-front allocation of bounce buffers and allocating
them as necessary from ZONE_DMA32? once we have that, we should be
able to switch to swiotlb by default.

Cheers,
Muli
-- 
Muli Ben-Yehuda
http://www.mulix.org | http://mulix.livejournal.com/


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