From: Jiri Bohac <jbohac@suse.cz>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: Jiri Bohac <jbohac@suse.cz>,
netdev@vger.kernel.org,
Stephen Hemminger <shemminger@linux-foundation.org>,
Jay Vosburgh <fubar@us.ibm.com>,
Andy Gospodarek <andy@greyhouse.net>,
Benjamin Poirier <benjamin.poirier@polymtl.ca>
Subject: Re: [PATCH] bonding: fix bridged bonds in 802.3ad mode
Date: Thu, 21 Apr 2011 21:27:49 +0200 [thread overview]
Message-ID: <20110421192749.GA8732@midget.suse.cz> (raw)
In-Reply-To: <1303412899.3165.47.camel@bwh-desktop>
On Thu, Apr 21, 2011 at 08:08:19PM +0100, Ben Hutchings wrote:
> It seems to me that 1e253c3b8a1aeed51eef6fc366812f219b97de65 is bogus
> and should be reverted, rather than worked around by other drivers. We
> shouldn't enable non-conformant forwarding behaviour by default just
> because some people find it useful. The administrator should have to
> explicitly enable it.
This is what I thought as well. I find it even more awkward to
make this behaviour dependend on the STP setting of the bridge
(turning on STP works around this bonding problem, btw).
But even if forwarding of link-local frames is made optional in
some way, it will still break bonding when turned on. So unless
this it is completely reverted, we still need some kind of fix
for bonding.
Btw, this could also be fixed by checking for
skb->protocol == htons(ETH_P_SLOW) directly in the bridging code.
However, I think the wonderful rx_handler infrastructure makes it
much cleaner this way...
--
Jiri Bohac <jbohac@suse.cz>
SUSE Labs, SUSE CZ
next prev parent reply other threads:[~2011-04-21 19:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 18:47 [PATCH] bonding: fix bridged bonds in 802.3ad mode Jiri Bohac
2011-04-21 19:08 ` Ben Hutchings
2011-04-21 19:27 ` Jiri Bohac [this message]
2011-04-21 20:43 ` Benjamin Poirier
2011-04-21 21:08 ` Stephen Hemminger
2011-04-22 4:19 ` David Miller
2011-04-22 15:27 ` Stephen Hemminger
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=20110421192749.GA8732@midget.suse.cz \
--to=jbohac@suse.cz \
--cc=andy@greyhouse.net \
--cc=benjamin.poirier@polymtl.ca \
--cc=bhutchings@solarflare.com \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.