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

[Xen-devel] Swiotlb

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Swiotlb
From: Kieran Mansley <kmansley@xxxxxxxxxxxxxx>
Date: Thu, 05 Apr 2007 15:23:41 +0100
Delivery-date: Thu, 05 Apr 2007 07:22:31 -0700
Envelope-to: www-data@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/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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
While writing a driver for a device doing lots of DMA I've hit an
"swiotlb_full()" problem.  This surprised me somewhat as I wouldn't have
expected to need the use of the software TLB - it's a 64 bit capable
device on a server with only 2 GB of RAM, and so I'd have expected to be
using a hardware TLB.  Is this a peculiarity of Xen, or should I be
right to be surprised?

I expect I can increase the size of the swiotlb to avoid this problem,
but thought I'd check that there isn't something more fundamentally
wrong first.

Thanks

Kieran


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

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