From: roopa <roopa@cumulusnetworks.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Guenter Roeck <linux@roeck-us.net>,
Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org, davem@davemloft.net,
vivien.didelot@savoirfairelinux.com,
jerome.oufella@savoirfairelinux.com, cphealy@gmail.com
Subject: Re: [PATCH RFC 2/2] net: dsa: bcm_sf2: implement HW bridging operations
Date: Thu, 19 Feb 2015 18:51:06 -0800 [thread overview]
Message-ID: <54E6A11A.2060703@cumulusnetworks.com> (raw)
In-Reply-To: <20150220021843.GG795@lunn.ch>
On 2/19/15, 6:18 PM, Andrew Lunn wrote:
>>> Remember that we are dealing with hardware switch chips. Those chips
>>> won't time out fdb entries just because the kernel's bridge driver
>>> thinks that it should.
>> Oh, they dont..?
> To some extent, it is better to think of these as two switches
> connected to each other, not one switch. The HW switch needs help with
> STP, but otherwise it is a fully functional and autonomous switch.
yes, exactly.
>
> This is going to make displaying the forwarding database interesting,
> because the SW bridge fdb and the HW bridge fdb are each subsets of
> the big picture and possible even contradictory since they are not
> updated atomically.
>
What we do on our switches is,
- disable SW bridge learning
- enable HW bridge learning
- we keep the SW bridge fdb in sync with the HW fdb, which leads to:
- HW learnt entries are pushed to SW bridge fdb
- SW static fdb entries (added by the user) are pushed to HW
next prev parent reply other threads:[~2015-02-20 2:51 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 19:26 [PATCH RFC 0/2] net: dsa: integration with SWITCHDEV for HW bridging Florian Fainelli
2015-02-17 19:26 ` [PATCH RFC 1/2] net: dsa: integrate " Florian Fainelli
2015-02-17 20:13 ` Guenter Roeck
2015-02-17 20:24 ` Florian Fainelli
2015-02-17 20:28 ` Guenter Roeck
2015-02-18 1:19 ` Andrew Lunn
2015-02-18 1:43 ` Florian Fainelli
2015-02-18 3:53 ` Guenter Roeck
2015-02-18 4:53 ` Florian Fainelli
2015-02-18 6:14 ` Guenter Roeck
2015-02-18 13:49 ` Andrew Lunn
2015-02-18 14:05 ` Guenter Roeck
2015-02-23 2:20 ` Guenter Roeck
2015-02-23 3:14 ` Andrew Lunn
2015-02-23 4:07 ` Guenter Roeck
2015-02-23 4:22 ` Andrew Lunn
2015-02-23 4:33 ` Florian Fainelli
2015-02-23 4:38 ` Guenter Roeck
2015-02-23 4:43 ` Florian Fainelli
2015-02-23 6:19 ` Guenter Roeck
2015-02-23 13:34 ` Andrew Lunn
2015-02-23 14:23 ` Guenter Roeck
2015-02-23 16:01 ` Andrew Lunn
2015-02-23 18:05 ` Florian Fainelli
2015-02-23 18:35 ` Guenter Roeck
2015-02-25 13:43 ` Andrey Volkov
2015-02-25 14:25 ` Guenter Roeck
2015-02-25 16:05 ` Andrey Volkov
2015-02-25 17:41 ` Guenter Roeck
2015-02-26 1:18 ` Andrey Volkov
2015-02-27 17:09 ` Andrey Volkov
2015-02-28 7:53 ` Guenter Roeck
2015-03-02 14:38 ` Andrey Volkov
2015-03-02 14:49 ` Guenter Roeck
2015-03-02 15:27 ` Andrey Volkov
2015-03-02 17:16 ` Guenter Roeck
2015-03-04 10:07 ` Andrey Volkov
2015-02-17 19:26 ` [PATCH RFC 2/2] net: dsa: bcm_sf2: implement HW bridging operations Florian Fainelli
2015-02-19 2:48 ` Florian Fainelli
2015-02-19 5:59 ` Guenter Roeck
2015-02-19 17:27 ` Florian Fainelli
2015-02-19 17:46 ` Guenter Roeck
2015-02-19 23:50 ` Florian Fainelli
2015-02-20 0:09 ` Guenter Roeck
2015-02-20 0:51 ` roopa
2015-02-20 1:03 ` Guenter Roeck
2015-02-20 1:46 ` roopa
2015-02-20 2:00 ` Florian Fainelli
2015-02-20 2:41 ` roopa
2015-02-20 4:05 ` Guenter Roeck
2015-02-20 4:58 ` Scott Feldman
2015-02-20 4:59 ` roopa
2015-02-20 3:20 ` Andy Gospodarek
2015-02-20 3:53 ` Viswanath Bandaru
2015-02-20 3:56 ` Andy Gospodarek
2015-02-20 2:18 ` Andrew Lunn
2015-02-20 2:51 ` roopa [this message]
2015-02-20 3:52 ` Andrew Lunn
2015-02-20 4:07 ` Guenter Roeck
2015-02-20 2:02 ` Andrew Lunn
2015-02-20 3:55 ` Guenter Roeck
2015-02-20 2:03 ` Florian Fainelli
2015-02-20 2:46 ` roopa
2015-02-18 0:48 ` [PATCH RFC 0/2] net: dsa: integration with SWITCHDEV for HW bridging Scott Feldman
2015-02-18 1:09 ` Florian Fainelli
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=54E6A11A.2060703@cumulusnetworks.com \
--to=roopa@cumulusnetworks.com \
--cc=andrew@lunn.ch \
--cc=cphealy@gmail.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=jerome.oufella@savoirfairelinux.com \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.com \
/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;
as well as URLs for NNTP newsgroup(s).