Mon, Mar 30, 2009 at 02:04:25PM CEST, kaber@xxxxxxxxx wrote: > David Miller wrote: >> From: Patrick McHardy <kaber@xxxxxxxxx> >> Date: Fri, 27 Mar 2009 08:53:13 +0100 >> >>> ... an alternative approach >>> would be to have bonding add FDB entries for all secondary MACs to >>> make bridging treat them as local. >> >> Do you guys foresee any possibility of an alternative implementation >> any time soon? >> >> Otherwise we're just stalling by not putting something into the tree, >> and as far as I can tell this patch here might as well be it. > > Adding bridge FDB entries seems like the best fix. It might > need some minor ugliness to avoid new dependencies between > bonding and bridging, but it definitely beats having new hooks > in the core in my opinion. Agree with this. > > But I have no idea whether Jiri is actually implementing this. Currently I'm thinking the way. What I have on mind: I would like to add a list into struct net_device to contain all mac addresses of the device. I would also like to use similar interface to handle them as currently is for uc_list and mc_list. However I do not like that these lists are not using standard list_head but they are propriate lists only for this purpose. I'm thinking about converting them to use list_head first. Or maybe ignore them and do the new list for macs in parallel? Then we can fill this list with macs in bonding driver and let bridge check it and make fdb entries. _______________________________________________ Bridge mailing list Bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/bridge
