willy tarreau wrote:
>
> Hello Thomas,
>
> I've modified the slaves lists as you suggested to me.
> The more I tried to optimize the code, the more it looked like
> 2.4's, so it seems the last one is already optimal. There's no
> slave_queue anymore, and the transmit path in bond_xmit_roundrobin
Hello Thomas,
I've modified the slaves lists as you suggested to me.
The more I
tried to optimize the code, the more it looked like
2.4's, so it
seems the last one is already optimal. There's no
slave_queue
anymore, and the transmit path in bond_xmit_roundrobin
is far
faster.
I have also impleme
willy tarreau wrote:
>
> > rename bond_xmit to bond_xmit_roundrobin, so
> > bond_xmit_xor can be implemented, and used if
> > desired. bond_xmit_xor is what cisco
> > etherchannel/sun trunking really uses, not round
> > robin.
>
> how does their xor method work ? do you know about an
> RFC stat
> rename bond_xmit to bond_xmit_roundrobin, so
> bond_xmit_xor can be implemented, and used if
> desired. bond_xmit_xor is what cisco
> etherchannel/sun trunking really uses, not round
> robin.
how does their xor method work ? do you know about an
RFC stating about this, that I could read ? I'm
Willy TARREAU wrote:
>
> Hello Thomas !
>
> I've slightly enhanced the bonding code :
> - MII link checking with automatic slave enabling/disabling :
> Now the bond interface monitors all its MII-compliant slaves
> and disables the ones which have a dead link, and enables those
> w
Hello Thomas !
I've slightly enhanced the bonding code :
- MII link checking with automatic slave enabling/disabling :
Now the bond interface monitors all its MII-compliant slaves
and disables the ones which have a dead link, and enables those
which have a good one. The link check t
6 matches
Mail list logo
