netdev - Re: [PATCH] bonding: ignore updelay param when there is no active slave

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] [day] [month] [year] [list]

Message-Id: <20090427.025803.183811676.davem@davemloft.net>
Date:	Mon, 27 Apr 2009 02:58:03 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jpirko@...hat.com
Cc:	netdev@...r.kernel.org, fubar@...ibm.com,
	bonding-devel@...ts.sourceforge.net
Subject: Re: [PATCH] bonding: ignore updelay param when there is no active
 slave

From: Jiri Pirko <jpirko@...hat.com>
Date: Fri, 24 Apr 2009 15:57:29 +0200

> Pointed out by Sean E. Millichamp.
> 
> Quote from Documentation/networking/bonding.txt:
> "Note that when a bonding interface has no active links, the
> driver will immediately reuse the first link that goes up, even if the
> updelay parameter has been specified (the updelay is ignored in this
> case).  If there are slave interfaces waiting for the updelay timeout
> to expire, the interface that first went into that state will be
> immediately reused.  This reduces down time of the network if the
> value of updelay has been overestimated, and since this occurs only in
> cases with no connectivity, there is no additional penalty for
> ignoring the updelay."
> 
> This patch actually changes the behaviour in this way.
> 
> Signed-off-by: Jiri Pirko <jpirko@...hat.com>

Applied to net-next-2.6
--
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