Re: [RFC PATCH net-next] bonding: add a vlan+srcmac tx hashing option
From: Jiri Pirko <jiri@resnulli.us>
Date: 2021-01-08 13:13:44
Also in:
lkml
Fri, Jan 08, 2021 at 12:58:13AM CET, jarod@redhat.com wrote:
On Mon, Dec 28, 2020 at 11:11:45AM +0100, Jiri Pirko wrote:quoted
Fri, Dec 18, 2020 at 08:30:33PM CET, jarod@redhat.com wrote:quoted
This comes from an end-user request, where they're running multiple VMs on hosts with bonded interfaces connected to some interest switch topologies, where 802.3ad isn't an option. They're currently running a proprietary solution that effectively achieves load-balancing of VMs and bandwidth utilization improvements with a similar form of transmission algorithm. Basically, each VM has it's own vlan, so it always sends its traffic out the same interface, unless that interface fails. Traffic gets split between the interfaces, maintaining a consistent path, with failover still available if an interface goes down. This has been rudimetarily tested to provide similar results, suitable for them to use to move off their current proprietary solution. Still on the TODO list, if these even looks sane to begin with, is fleshing out Documentation/networking/bonding.rst.Jarod, did you consider using team driver instead ? :)That's actually one of the things that was suggested, since team I believe already has support for this, but the user really wants to use bonding. We're finding that a lot of users really still prefer bonding over team.
Do you know the reason, other than "nostalgia"?