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: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Tue, 20 Mar 2007 10:18:54 +0000
Cc: Xen Development Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir@xxxxxxxxxxxxx>
Delivery-date: Tue, 20 Mar 2007 03:18:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070320101140.GA19380@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acdq2Sl/aBo/StbMEduzOgAX8io7RQ==
Thread-topic: [Xen-devel] RFC: [0/2] Remove netloop by lazy copying in netback
User-agent: Microsoft-Entourage/11.2.5.060620
On 20/3/07 10:11, "Herbert Xu" <herbert@xxxxxxxxxxxxxxxxxxx> wrote:

> Yes that's a good idea and would avoid the grant table addition.
> 
> My only concern would be future acceptance into the mainstream
> Linux kernel, especially on the domU side since I'd like to see
> this idea used for dom0 => domU as well.
> 
> However, I'm certainly happy to explore doing it in the way you
> suggested.

That's quite a valid concern, but I think that the required addition to the
#PF handler (certainly for i386 and x86/64) will be clean and small, and it
will not affect #PF critical-path latencies. I'd be fairly optimistic about
it getting accepted upstream, perhaps modulo concerns over whether we'd need
to implement it for *every* architecture.

 -- Keir


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