From: David Miller <davem@davemloft.net>
To: ole@ans.pl
Cc: fubar@us.ibm.com, bonding-devel@lists.sourceforge.net,
netdev@vger.kernel.org
Subject: Re: [net-next-2.6 PATCH 3/3] bonding: reread information about speed and duplex when interface goes up
Date: Wed, 06 Oct 2010 14:28:31 -0700 (PDT) [thread overview]
Message-ID: <20101006.142831.102541368.davem@davemloft.net> (raw)
In-Reply-To: <4ca4b87e.NzbQ35P2qRrA2iuz%ole@ans.pl>
From: Krzysztof Piotr Oledzki <ole@ans.pl>
Date: Thu, 30 Sep 2010 18:19:10 +0200
>>From 43285224a785e90c7d4cff2be0766ca8df6ddfb9 Mon Sep 17 00:00:00 2001
> From: Krzysztof Piotr Oledzki <ole@ans.pl>
> Date: Thu, 30 Sep 2010 17:09:02 +0200
> Subject: bonding: reread information about speed and duplex when interface goes up
>
> When an interface was enslaved when it was down, bonding thinks
> it has speed -1 even after it goes up. This leads into selecting
> a wrong active interface in active/backup mode on mixed 10G/1G or
> 1G/100M environment.
>
> before:
> bonding: bond0: link status definitely up for interface eth5, 100 Mbps full duplex.
> bonding: bond0: link status definitely up for interface eth0, 100 Mbps full duplex.
>
> after:
> bonding: bond0: link status definitely up for interface eth5, 10000 Mbps full duplex.
> bonding: bond0: link status definitely up for interface eth0, 1000 Mbps full duplex.
>
> Signed-off-by: Krzysztof Piotr Oledzki <ole@ans.pl>
Applied.
prev parent reply other threads:[~2010-10-06 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 16:19 [net-next-2.6 PATCH 3/3] bonding: reread information about speed and duplex when interface goes up Krzysztof Piotr Oledzki
2010-10-06 21:28 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101006.142831.102541368.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bonding-devel@lists.sourceforge.net \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=ole@ans.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox