Dilip Daya <dilip.daya@xxxxxx> writes: > Hi Eric, > We do need to move bonds between namespaces - because we require > physical interfaces in each namespace -- we don't want the overheads of > virtual interfaces, don't have the management infrastructure, and don't > want to manufacture fake mac addresses that would be required for > macvlan interfaces. Since the bonds are implicitly created in the host > namespace, the only way we know to get bonds directly into the > namespaces is to move them. There about 3 ways to create bonding devices. One of those ways is to create bonding devices when loading the module. Another way is to create a bond device with "echo '+bond35 > /sys/class/net/bonding_masters". them when loading the module, and my favorite is the standard way "ip link add type bond". All but loading the bonding device work in the network namespace you are in at the type. > Would "NETDEV_UNREGISTER and NETDEV_REGISTER events to remove/add the > per device proc files at the appropriate time." help in the case? Yes. But since you can create the bonding device in the network namespace you need it in, I don't see the point, of adding a code path no one will test for 3 years at a time. It seems easier to me to just not allow migration of bonding devices and set peoples expectations a little lower. Especially given the very complex user space interfaces. On ther other hand if you want to write and test and generally own the patch I will review it. Eric _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/containers
