From: Florian Fainelli <f.fainelli@gmail.com>
To: Vladimir Oltean <olteanv@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Cc: Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Vladimir Oltean <vladimir.oltean@nxp.com>
Subject: Re: [PATCH net-next 3/6] net: dsa: execute dsa_switch_mdb_add only for routing port in cross-chip topologies
Date: Sun, 20 Jun 2021 07:24:40 -0700 [thread overview]
Message-ID: <53938405-2ba4-558f-4f2e-b7fbca846636@gmail.com> (raw)
In-Reply-To: <20210618183017.3340769-4-olteanv@gmail.com>
On 6/18/2021 11:30 AM, Vladimir Oltean wrote:
> From: Vladimir Oltean <vladimir.oltean@nxp.com>
>
> Currently, the notifier for adding a multicast MAC address matches on
> the targeted port and on all DSA links in the system, be they upstream
> or downstream links.
>
> This leads to a considerable amount of useless traffic.
>
> Consider this daisy chain topology, and a MDB add notifier emitted on
> sw0p0. It matches on sw0p0, sw0p3, sw1p3 and sw2p4.
>
> sw0p0 sw0p1 sw0p2 sw0p3 sw0p4
> [ user ] [ user ] [ user ] [ dsa ] [ cpu ]
> [ x ] [ ] [ ] [ x ] [ ]
> |
> +---------+
> |
> sw1p0 sw1p1 sw1p2 sw1p3 sw1p4
> [ user ] [ user ] [ user ] [ dsa ] [ dsa ]
> [ ] [ ] [ ] [ x ] [ x ]
> |
> +---------+
> |
> sw2p0 sw2p1 sw2p2 sw2p3 sw2p4
> [ user ] [ user ] [ user ] [ user ] [ dsa ]
> [ ] [ ] [ ] [ ] [ x ]
>
> But switch 0 has no reason to send the multicast traffic for that MAC
> address on sw0p3, which is how it reaches switches 1 and 2. Those
> switches don't expect, according to the user configuration, to receive
> this multicast address from switch 1, and they will drop it anyway,
> because the only valid destination is the port they received it on.
> They only need to configure themselves to deliver that multicast address
> _towards_ switch 1, where the MDB entry is installed.
>
> Similarly, switch 1 should not send this multicast traffic towards
> sw1p3, because that is how it reaches switch 2.
>
> With this change, the heat map for this MDB notifier changes as follows:
>
> sw0p0 sw0p1 sw0p2 sw0p3 sw0p4
> [ user ] [ user ] [ user ] [ dsa ] [ cpu ]
> [ x ] [ ] [ ] [ ] [ ]
> |
> +---------+
> |
> sw1p0 sw1p1 sw1p2 sw1p3 sw1p4
> [ user ] [ user ] [ user ] [ dsa ] [ dsa ]
> [ ] [ ] [ ] [ ] [ x ]
> |
> +---------+
> |
> sw2p0 sw2p1 sw2p2 sw2p3 sw2p4
> [ user ] [ user ] [ user ] [ user ] [ dsa ]
> [ ] [ ] [ ] [ ] [ x ]
>
> Now the mdb notifier behaves the same as the fdb notifier.
>
> Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
--
Florian
next prev parent reply other threads:[~2021-06-20 14:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 18:30 [PATCH net-next 0/6] Improvement for DSA cross-chip setups Vladimir Oltean
2021-06-18 18:30 ` [PATCH net-next 1/6] net: dsa: assert uniqueness of dsa,member properties Vladimir Oltean
2021-06-19 1:59 ` Florian Fainelli
2021-06-21 13:53 ` Andrew Lunn
2021-06-18 18:30 ` [PATCH net-next 2/6] net: dsa: export the dsa_port_is_{user,cpu,dsa} helpers Vladimir Oltean
2021-06-19 2:00 ` Florian Fainelli
2021-06-21 13:55 ` Andrew Lunn
2021-06-18 18:30 ` [PATCH net-next 3/6] net: dsa: execute dsa_switch_mdb_add only for routing port in cross-chip topologies Vladimir Oltean
2021-06-20 14:24 ` Florian Fainelli [this message]
2021-06-18 18:30 ` [PATCH net-next 4/6] net: dsa: calculate the largest_mtu across all ports in the tree Vladimir Oltean
2021-06-20 14:23 ` Florian Fainelli
2021-06-18 18:30 ` [PATCH net-next 5/6] net: dsa: targeted MTU notifiers should only match on one port Vladimir Oltean
2021-06-20 14:25 ` Florian Fainelli
2021-06-18 18:30 ` [PATCH net-next 6/6] net: dsa: remove cross-chip support from the MRP notifiers Vladimir Oltean
2021-06-20 14:22 ` 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=53938405-2ba4-558f-4f2e-b7fbca846636@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.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).