On Fri, 25 Nov 2011 06:24:36 -0500 jamal <h...@cyberus.ca> wrote: > Most hardware bridges out there support all different modes: > You can have learning in the hardware or defer it to user/control plane > by setting some flags. You can have broadcasting done in hardware or > defer to user space. > The mods i was thinking of is to bring the Linux bridge to have the > same behavior. You then need to allow netlink updates of bridge MAC > table from user space. There may be weaknesses with the current bridging > code in relation to Vlans that may need to be addressed. > > [But my concern was not so much the bridge - because changes are needed > in that case; it is the "match, actionlist" that is already in place > that got to me.]
The bridge module is already overly complex. Rather than adding more modes, it should be split into separate modules. If you look at macvlan, you will see it is already a subset of to bridge. Another example of this is the team driver which is really just a subset of the bonding code. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
