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] RFC: [0/2] Remove netloop by lazy copying in netback

To: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] RFC: [0/2] Remove netloop by lazy copying in netback
From: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Date: Tue, 27 Mar 2007 17:22:31 +0900
Cc: Xen Development Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 27 Mar 2007 01:26:56 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070327075318.GA24443@xxxxxxxxxxxxxxxxxxx>
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: <C22E8817.4DCC%Keir.Fraser@xxxxxxxxxxxx> <C22E8B83.4E63%Keir.Fraser@xxxxxxxxxxxx> <20070327075318.GA24443@xxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.2.1i
On Tue, Mar 27, 2007 at 05:53:18PM +1000, Herbert Xu wrote:
> On Tue, Mar 27, 2007 at 08:51:15AM +0100, Keir Fraser wrote:
> > 
> > Also bear in mind the plan to avoid the grant mapping at all in the
> > direct-to-wire transmit case. This also will rely on a #PF (or some other
> > fault, potentially) if the guest tries to access that pseudophysical page of
> > memory. If we can work out a way to make this work on ia64 then the
> > delayed-copy implementation problems are solved too.
> That's to avoid the TLB flush costs, right?

Xen/IA64 has optimization there. Xen/ia64 tracks tlb inserts
on grant table mapped page.
If there was no tlb insert(i.e. direct-to-wire transmit case),
it doesn't issue tlb flush, but only clears the p2m entry
when grant table unmap.

On Xen/IA64 case, something like copy-on-demand-access can be implemented
as copy-on-tlb-insert in xen, I suppose.

-- 
yamahata

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

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