From: Stephen Hemminger <stephen@networkplumber•org>
To: Nikolay Aleksandrov <razor@blackwall•org>
Cc: vyasevic@redhat•com, bridge@lists•linux-foundation.org,
Nikolay Aleksandrov <nikolay@cumulusnetworks•com>,
netdev@vger•kernel.org, wkok@cumulusnetworks•com,
davem@davemloft•net
Subject: Re: [PATCH net-next v2] bridge: vlan: allow to suppress local mac install for all vlans
Date: Tue, 25 Aug 2015 17:56:27 -0700 [thread overview]
Message-ID: <20150825175627.66ca9f30@urahara> (raw)
In-Reply-To: <1440549295-3979-1-git-send-email-razor@blackwall.org>
On Tue, 25 Aug 2015 17:34:55 -0700
Nikolay Aleksandrov <razor@blackwall•org> wrote:
> From: Nikolay Aleksandrov <nikolay@cumulusnetworks•com>
>
> This patch adds a new knob that, when enabled, allows to suppress the
> installation of local fdb entries in newly created vlans. This could
> pose a big scalability issue if we have a large number of ports and a
> large number of vlans, e.g. in a 48 port device with 2000 vlans these
> entries easily go up to 96000.
> Note that packets for these macs are still received properly because they
> are added in vlan 0 as "own" macs and referenced when fdb lookup by vlan
> results in a miss.
> Also note that vlan membership of ingress port and the bridge device
> as egress are still being correctly enforced.
>
> The default (0/off) is keeping the current behaviour.
>
> Based on a patch by Wilson Kok (wkok@cumulusnetworks•com).
This is getting messy, but then again the bridge seems to have become
a ghetto for a long time. I would rather see the lookup code fixed so
that the fdb was correct.
next prev parent reply other threads:[~2015-08-26 0:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 0:34 [PATCH net-next v2] bridge: vlan: allow to suppress local mac install for all vlans Nikolay Aleksandrov
2015-08-26 0:56 ` Stephen Hemminger [this message]
2015-08-26 5:42 ` Nikolay Aleksandrov
2015-08-26 0:58 ` Stephen Hemminger
2015-08-26 2:42 ` David Miller
2015-08-26 5:28 ` Nikolay Aleksandrov
2015-08-26 6:06 ` David Miller
2015-08-26 11:33 ` Nikolay Aleksandrov
2015-08-27 4:57 ` roopa
2015-08-27 21:02 ` Nikolay Aleksandrov
2015-08-27 23:47 ` Vlad Yasevich
2015-08-28 2:17 ` Nikolay Aleksandrov
2015-08-28 12:31 ` Vlad Yasevich
2015-08-28 15:26 ` Nikolay Aleksandrov
2015-08-29 1:11 ` Vlad Yasevich
2015-09-13 13:22 ` Nikolay Aleksandrov
2015-08-26 6:10 ` B Viswanath
2015-08-26 12:52 ` Vlad Yasevich
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=20150825175627.66ca9f30@urahara \
--to=stephen@networkplumber$(echo .)org \
--cc=bridge@lists$(echo .)linux-foundation.org \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nikolay@cumulusnetworks$(echo .)com \
--cc=razor@blackwall$(echo .)org \
--cc=vyasevic@redhat$(echo .)com \
--cc=wkok@cumulusnetworks$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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