| Message ID | 1392433180-16052-5-git-send-email-mcgrof@do-not-panic.com |
|---|---|
| State | RFC, archived |
| Delegated to: | David Miller |
| Headers | show |
There is a valid scenario to put IP addresses on the backend VIFs: http://wiki.xen.org/wiki/Xen_Networking#Routing Also, the backend is not necessarily Dom0, you can connect twou guests with backend/frontend pairs. Zoli On 15/02/14 02:59, Luis R. Rodriguez wrote: > From: "Luis R. Rodriguez" <mcgrof@suse.com> > > The xen-netback driver is used only to provide a backend > interface for the frontend. The link is the only thing we > use, and that is used internally for letting us know when the > xen-netfront is ready, when it switches to XenbusStateConnected. > > Note that only when the both the xen-netfront and xen-netback > are both in state XenbusStateConnected will xen-netback allow > userspace on the host (backend) to bring up the interface. Enabling > and disabling the interface will simply enable or disable NAPI > respectively, and that's used for IRQ communication set up with > the xen event channels. > > Cc: Paul Durrant <Paul.Durrant@citrix.com> > Cc: Ian Campbell <ian.campbell@citrix.com> > Cc: Wei Liu <wei.liu2@citrix.com> > Cc: xen-devel@lists.xenproject.org > Cc: netdev@vger.kernel.org > Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com> > --- > drivers/net/xen-netback/interface.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/net/xen-netback/interface.c b/drivers/net/xen-netback/interface.c > index d380e3f..07e6fd2 100644 > --- a/drivers/net/xen-netback/interface.c > +++ b/drivers/net/xen-netback/interface.c > @@ -351,7 +351,7 @@ struct xenvif *xenvif_alloc(struct device *parent, domid_t domid, > > eth_hw_addr_random(dev); > memcpy(dev->dev_addr, xen_oui, 3); > - dev->priv_flags |= IFF_BRIDGE_NON_ROOT; > + dev->priv_flags |= IFF_BRIDGE_NON_ROOT | IFF_SKIP_IP; > netif_napi_add(dev, &vif->napi, xenvif_poll, XENVIF_NAPI_WEIGHT); > > netif_carrier_off(dev); > -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, Feb 17, 2014 at 6:36 AM, Zoltan Kiss <zoltan.kiss@citrix.com> wrote: > There is a valid scenario to put IP addresses on the backend VIFs: > > http://wiki.xen.org/wiki/Xen_Networking#Routing This is useful thanks! > Also, the backend is not necessarily Dom0, you can connect two guests with > backend/frontend pairs. Can you elaborate a bit more on this type of setup? Luis -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, 2014-02-18 at 12:16 -0800, Luis R. Rodriguez wrote: > On Mon, Feb 17, 2014 at 6:36 AM, Zoltan Kiss <zoltan.kiss@citrix.com> wrote: > > Also, the backend is not necessarily Dom0, you can connect two guests with > > backend/frontend pairs. > > Can you elaborate a bit more on this type of setup? The domain providing backend networking services is not necessarily dom0, it might be a driver domain: http://wiki.xen.org/wiki/Driver_Domain I think from your PoV here it probably doesn't matter whether the driver domain is dom0 or some other domain. Ian. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/drivers/net/xen-netback/interface.c b/drivers/net/xen-netback/interface.c index d380e3f..07e6fd2 100644 --- a/drivers/net/xen-netback/interface.c +++ b/drivers/net/xen-netback/interface.c @@ -351,7 +351,7 @@ struct xenvif *xenvif_alloc(struct device *parent, domid_t domid, eth_hw_addr_random(dev); memcpy(dev->dev_addr, xen_oui, 3); - dev->priv_flags |= IFF_BRIDGE_NON_ROOT; + dev->priv_flags |= IFF_BRIDGE_NON_ROOT | IFF_SKIP_IP; netif_napi_add(dev, &vif->napi, xenvif_poll, XENVIF_NAPI_WEIGHT); netif_carrier_off(dev);