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] SWIOMMU redundant copies?

To: "Stephen C. Tweedie" <sct@xxxxxxxxxx>
Subject: Re: [Xen-devel] SWIOMMU redundant copies?
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 14 Mar 2008 16:39:23 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 14 Mar 2008 09:40:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1205512470.8010.36.camel@xxxxxxxxxxxxxxxxxxxxx>
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
Thread-index: AciF8fVaM8CrWvHlEdyPnAAWy6hiGQ==
Thread-topic: [Xen-devel] SWIOMMU redundant copies?
User-agent: Microsoft-Entourage/11.3.6.070618
On 14/3/08 16:34, "Stephen C. Tweedie" <sct@xxxxxxxxxx> wrote:

>> Yes, the swiotlb check could be relaxed. Do we really do many mergeable
>> page-straddling I/Os in practice though? I would expect most block I/O to be
>> scattered by the page cache.
> 
> I would, too --- but it appears to be a genuine issue at boot time at
> least, when the page cache has not yet become too fragmented.
> 
> I'm still trying to understand the corner cases involved.  Some
> hardware seems to have more trouble than others --- it could well be
> special-case sg segments such as DMA drain buffers which are causing the
> trouble for those, in which case doing the copy for every map_sg() will
> potentially be a significant problem.  (MarkMC hit that same problem
> bringing the dom0 patches onto 2.6.25 which has reworked drain buffer
> code.)

It certainly seems sensible to improve the page-discontiguity check.
Possibly we can stick it inside page_straddles_boundary() (perhaps with a
name change) and fix every caller.

Also, I agree it sounds like something fishier is going on and this is
perhaps only a workaround that fortuitously works in this case... :-(

 -- Keir



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

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