| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <5301E411.5060908@citrix.com> Date: Mon, 17 Feb 2014 10:27:29 +0000 From: David Vrabel <david.vrabel@...rix.com> To: "Luis R. Rodriguez" <mcgrof@...not-panic.com> CC: <netdev@...r.kernel.org>, <xen-devel@...ts.xenproject.org>, "Luis R. Rodriguez" <mcgrof@...e.com>, <linux-kernel@...r.kernel.org>, <kvm@...r.kernel.org> Subject: Re: [Xen-devel] [RFC v2 0/4] net: bridge / ip optimizations for virtual net backends On 15/02/14 02:59, Luis R. Rodriguez wrote: > From: "Luis R. Rodriguez" <mcgrof@...e.com> > > This v2 series changes the approach from my original virtualization > multicast patch series [0] by abandoning completely the multicast > issues and instead generalizing an approach for virtualization > backends. There are two things in common with virtualization > backends: > > 0) they should not become the root bridge > 1) they don't need ipv4 / ipv6 interfaces Why? There's no real difference between a backend network device and a physical device (from the point of view of the backend domain). I do not think these are intrinsic properties of backend devices. I can see these being useful knobs for administrators (or management toolstacks) to turn on, on a per-device basis. David -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists