All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Steven Smith <steven.smith@citrix.com>
Cc: Steven Smith <Steven.Smith@eu.citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Keir Fraser <Keir.Fraser@eu.citrix.com>,
	"joserenato.santos@hp.com" <joserenato.santos@hp.com>
Subject: Re: [PATCH 00/17] Netchannel2 for a modern git kernel
Date: Tue, 06 Oct 2009 10:06:17 -0700	[thread overview]
Message-ID: <4ACB7909.7000804@goop.org> (raw)
In-Reply-To: <20091006090616.GA21511@weybridge.uk.xensource.com>

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

  parent reply	other threads:[~2009-10-06 17:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1254667618.git.ssmith@weybridge.uk.xensource.com>
2009-10-04 15:04 ` [PATCH 10/17] Transmit and receive checksum offload support steven.smith
2009-10-04 23:09 ` [PATCH 00/17] Netchannel2 for a modern git kernel Jeremy Fitzhardinge
2009-10-05  9:29   ` Steven Smith
2009-10-05 21:22     ` Jeremy Fitzhardinge
2009-10-06  9:06       ` Steven Smith
2009-10-06 16:35         ` Steven Smith
2009-10-06 17:12           ` Jeremy Fitzhardinge
2009-10-07 19:17             ` Steven Smith
2009-10-06 17:06         ` Jeremy Fitzhardinge [this message]
2009-10-07  8:15           ` Steven Smith
2009-10-20  6:00             ` Jeremy Fitzhardinge
2009-10-20  9:40               ` Steven Smith
2009-10-23 22:06                 ` Jeremy Fitzhardinge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4ACB7909.7000804@goop.org \
    --to=jeremy@goop.org \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=Steven.Smith@eu.citrix.com \
    --cc=joserenato.santos@hp.com \
    --cc=steven.smith@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.