netdev - Re: Bonding problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 8 Aug 2011 12:26:45 -0400
From:	Andy Gospodarek <andy@...yhouse.net>
To:	Eduard Sinelnikov <eduard.sinelnikov@...il.com>
Cc:	majordomo@...r.kernel.org, netdev@...r.kernel.org,
	Jay Vosburgh <fubar@...ibm.com>,
	Andy Gospodarek <andy@...yhouse.net>
Subject: Re: Bonding problem

On Sun, Aug 07, 2011 at 03:00:30PM +0300, Eduard Sinelnikov wrote:
> Hi,
> 
> In the kernel 2.6.39.3 ( /drivers/net/bond/bond_main.c).
> In the function  ‘bond_xmit_roundrobin’
> The code check if the bond is active via
> ‘bond_is_active_slave(slave)’ Function call.
> Which actually checks if the slave is backup or active
> What is the meaning of slave being  backup in round robin mode?
> Correct me if I wrong but in round robin every slave should send a
> packet, regardless of being active or backup.
> 
> Thank you,
>            Eduard

There probably is not a compelling reason to continue to have it.  There
may be a reason historically, but I'm not aware what that might be at
this point.  For modes other than active-backup, the value of
slave->link and slave->backup should always contain a value that
indicates the slave is up and available for transmit.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html