On Fri, 2016-09-02 at 18:25 +0200, Jiri Pirko wrote: > Understand the reason. All I say is we tried hard (I surely did) in > the past to remove bonding specific quirks and now we are adding one. > And the simple reason is that the code is such a mess. > > Just use team instead and you'll be fine. You can "google" it :)
Sure, please join _our_ team and make all the needed changes in user land. The kernel part of it is epsilon compared to all the control part (ie talk to the various Google switches.), and monitoring. I am fine to leave the bug in upstream bonding driver, if you really want to force people out of bonding land ! Here an automated test simply used macvlan and did not remove the macvlan before enslaving the netdev again in a bonding, we already fixed the test, because it is faster than deploying new kernels anyway.
