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] Re: [PATCH 00/17] Netchannel2 for a modern git kernel

To: Steven Smith <steven.smith@xxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH 00/17] Netchannel2 for a modern git kernel
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Tue, 06 Oct 2009 10:06:17 -0700
Cc: Steven Smith <Steven.Smith@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>, "joserenato.santos@xxxxxx" <joserenato.santos@xxxxxx>
Delivery-date: Tue, 06 Oct 2009 10:06:42 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20091006090616.GA21511@xxxxxxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <cover.1254667618.git.ssmith@xxxxxxxxxxxxxxxxxxxxxxxxxx> <4AC92B44.5020208@xxxxxxxx> <20091005092937.GA1036@xxxxxxxxxxxxxxxxxxxxxxxxxx> <4ACA638A.5060209@xxxxxxxx> <20091006090616.GA21511@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.1) Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Lightning/1.0pre Thunderbird/3.0b3
On 10/06/09 02:06, Steven Smith wrote:
>> Thanks.  I've pulled it anyway, but not yet merged it into anything yet.
>>     
> Okay.  I'm going to change the interface a bit following the review
> comments; would you prefer I shove a fixup patch on the end or edit
> history and keep the patches sensibly self-contained?
>   

At this point I haven't done anything with the branch, so just rewrite
it to your heart's content.

BTW, do you see this is something as a candidate for merging upstream?

> I needed to make some changes to netback to make forwarding packets
> between NC1 and NC2 interfaces work, but apart from that it's fairly
> self-contained.  Would you like me to rebase to
> xen/dom0/backend/netback?
>   

Yep, sounds good.

An outstanding problem with netback is how we can deal with "foreign"
pages in dom0's network stack.  The current approach isn't viable for
upstream, but there has only been slow movement in coming up with a
better approach.

I haven't looked at nc2 yet, but does it use the same technique for
memory management, or something else?

> It'd certainly be possible to create the three branches you suggest,
> but I'd guess you'd end up with almost everything going into the
> common branch with the frontend and backend branches containing a
> single patch each to add netfront2.c and netback2.c respectively.  I'm
> not sure how useful that would be.
>   

OK, one branch is fine.

    J

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