|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] Re: [PATCH] Remus breaks the build
To: |
Brendan Cully <brendan@xxxxxxxxx> |
Subject: |
Re: [Xen-devel] Re: [PATCH] Remus breaks the build |
From: |
Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> |
Date: |
Thu, 19 Aug 2010 15:38:00 +0100 |
Cc: |
Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "Xen-devel@xxxxxxxxxxxxxxxxxxx" <Xen-devel@xxxxxxxxxxxxxxxxxxx>, Dulloor <dulloor@xxxxxxxxx>, Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>, Stefano, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, "Stefano@xxxxxxxxx" <Stefano@xxxxxxxxx> |
Delivery-date: |
Thu, 19 Aug 2010 07:39:24 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<20100818175852.GB14363@xxxxxxxxxxxxxxxxx> |
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: |
<4C6493ED.3040605@xxxxxxxx> <20100813194217.GA6981@xxxxxxxxxxxxxxxxx> <4C65B5A5.8020202@xxxxxxxx> <AANLkTiktNSnHfF_v+L7Ad+6BcaYwuQVdWv1WKm_r7wFy@xxxxxxxxxxxxxx> <20100817173828.GA2898@xxxxxxxxxxxxxxxxx> <19563.58079.648445.441841@xxxxxxxxxxxxxxxxxxxxxxxx> <20100818175852.GB14363@xxxxxxxxxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Brendan Cully writes ("Re: [Xen-devel] Re: [PATCH] Remus breaks the build"):
> You are correct, the device is just plumbing. But it isn't any extra
> code, at least for pvops -- IFB is carried in upstream linux. You
> could probably use a second-level bridge or tap or policy routing or
> something to get the same effect, but I don't think I see the
> advantage. You're certainly welcome to put together an alternative
> approach for comparison.
Ah, I see. I hadn't realised it was in upstream. Fine, then.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|