On Fri, 2009-11-27 at 23:14 +0100, Arnd Bergmann wrote: > On Friday 13 November 2009, Patrick Mullaney wrote: > > > > The macvlan driver didn't allow for creation/deletion of devices > > by other in-kernel modules. This patch provides common routines > > for both in-kernel and netlink based management. This patch > > also enables macvlan device support for gro for lower level > > devices that support gro. > > I wonder if doing this way round is a good idea, why don't > you just use netlink to set up the endpoint device like > the current macvlan and macvtap do? I think doing it consistently > for all backends would be a significant advantage. sorry for the late response - I'm thinking about re-implementing this along the lines that you are talking about. Especially in light of your new configuration options. The reason(probably short sighted) for the previous approach was that the creation step was already being handled in our venet driver(but it doesn't have to be). Thanks for the suggestion. Patrick > > Arnd <>< _______________________________________________ Bridge mailing list Bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/bridge
