From: Andrew Lunn <andrew@lunn.ch>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: "Allan W. Nielsen" <allan.nielsen@microchip.com>,
"David S. Miller" <davem@davemloft.net>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Vivien Didelot <vivien.didelot@gmail.com>,
Joergen Andreasen <joergen.andreasen@microchip.com>,
Alexandru Marginean <alexandru.marginean@nxp.com>,
Claudiu Manoil <claudiu.manoil@nxp.com>,
Xiaoliang Yang <xiaoliang.yang_1@nxp.com>,
"Y.b. Lu" <yangbo.lu@nxp.com>, netdev <netdev@vger.kernel.org>,
Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>
Subject: Re: [PATCH v2 net-next 0/2] Allow unknown unicast traffic to CPU for Felix DSA
Date: Tue, 25 Feb 2020 14:37:28 +0100 [thread overview]
Message-ID: <20200225133728.GE9749@lunn.ch> (raw)
In-Reply-To: <CA+h21hp41WXXTLZ0L2rwT5b1gMeL5YFBpNpCZMh7d9eWZpmaqw@mail.gmail.com>
> Secondly, even traffic that the CPU _intends_ to terminate remains
> "unknown" from the switch's perspective, due to the
> no-learning-from-injected-traffic issue. So that traffic is still
> going to be flooded, potentially to unwanted ports as well.
Hi Vladimir
Can you add an entry to its table to solve this? Make it known
traffic. Hook into dsa_slave_set_rx_mode() and
dsa_slave_set_mac_address()?
Andrew
next prev parent reply other threads:[~2020-02-25 13:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 21:34 [PATCH v2 net-next 0/2] Allow unknown unicast traffic to CPU for Felix DSA Vladimir Oltean
2020-02-24 21:34 ` [PATCH v2 net-next 1/2] net: mscc: ocelot: eliminate confusion between CPU and NPI port Vladimir Oltean
2020-02-25 12:55 ` Allan W. Nielsen
2020-02-24 21:34 ` [PATCH v2 net-next 2/2] net: dsa: felix: Allow unknown unicast traffic towards the CPU port module Vladimir Oltean
2020-02-25 13:01 ` Allan W. Nielsen
2020-02-25 13:02 ` [PATCH v2 net-next 0/2] Allow unknown unicast traffic to CPU for Felix DSA Allan W. Nielsen
2020-02-25 13:08 ` Vladimir Oltean
2020-02-25 13:37 ` Andrew Lunn [this message]
2020-02-25 13:57 ` Vladimir Oltean
2020-02-25 13:43 ` Allan W. Nielsen
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=20200225133728.GE9749@lunn.ch \
--to=andrew@lunn.ch \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alexandru.marginean@nxp.com \
--cc=allan.nielsen@microchip.com \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=joergen.andreasen@microchip.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.com \
--cc=xiaoliang.yang_1@nxp.com \
--cc=yangbo.lu@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).