From: Vladimir Oltean <olteanv@gmail.com>
To: DENG Qingfang <dqfext@gmail.com>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
"Vivien Didelot" <vivien.didelot@gmail.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Russell King" <linux@armlinux.org.uk>,
"open list:NETWORKING DRIVERS" <netdev@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
"Ansuel Smith" <ansuelsmth@gmail.com>,
"Jonathan McDowell" <noodles@earth.li>,
"Michal Vokáč" <vokac.m@gmail.com>,
"Christian Lamparter" <chunkeey@gmail.com>,
"Nishka Dasgupta" <nishkadg.linux@gmail.com>,
"Xiaofei Shen" <xiaofeis@codeaurora.org>,
"John Crispin" <john@phrozen.org>,
"Stefan Lippers-Hollmann" <s.l-h@gmx.de>,
"Hannu Nyman" <hannu.nyman@iki.fi>,
"Imran Khan" <gururug@gmail.com>,
"Frank Wunderlich" <frank-w@public-files.de>,
"Nick Lowe" <nick.lowe@gmail.com>,
"André Valentin" <avalentin@vmh.kalnet.hooya.de>
Subject: Re: [RFC net-next 2/3] net: dsa: qca8k: enable assisted learning on CPU port
Date: Sun, 8 Aug 2021 01:25:55 +0300 [thread overview]
Message-ID: <20210807222555.y6r7qxhdyy6d3esx@skbuf> (raw)
In-Reply-To: <20210807120726.1063225-3-dqfext@gmail.com>
On Sat, Aug 07, 2021 at 08:07:25PM +0800, DENG Qingfang wrote:
> Enable assisted learning on CPU port to fix roaming issues.
'roaming issues' implies to me it suffered from blindness to MAC
addresses learned on foreign interfaces, which appears to not be true
since your previous patch removes hardware learning on the CPU port
(=> hardware learning on the CPU port was supported, so there were no
roaming issues)
>
> Although hardware learning is available, it won't work well with
> software bridging fallback or multiple CPU ports.
This part is potentially true however, but it would need proof. I am not
familiar enough with the qca8k driver to say for sure that it suffers
from the typical problem with bridging with software LAG uppers (no FDB
isolation for standalone ports => attempt to shortcircuit the forwarding
through the CPU port and go directly towards the bridged port, which
would result in drops), and I also can't say anything about its support
for multiple CPU ports.
next prev parent reply other threads:[~2021-08-07 22:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 12:07 [RFC net-next 0/3] qca8k bridge flags offload DENG Qingfang
2021-08-07 12:07 ` [RFC net-next 1/3] net: dsa: qca8k: offload bridge flags DENG Qingfang
2021-08-07 20:45 ` Vladimir Oltean
2021-08-07 12:07 ` [RFC net-next 2/3] net: dsa: qca8k: enable assisted learning on CPU port DENG Qingfang
2021-08-07 22:25 ` Vladimir Oltean [this message]
2021-08-08 16:05 ` DENG Qingfang
2021-08-08 21:10 ` Vladimir Oltean
2021-08-10 17:27 ` Andre Valentin
2021-08-10 17:53 ` Vladimir Oltean
2021-08-10 21:09 ` Andre Valentin
2021-08-10 23:33 ` Vladimir Oltean
2021-08-07 12:07 ` [RFC net-next 3/3] net: dsa: tag_qca: set offload_fwd_mark DENG Qingfang
2021-08-07 22:57 ` Vladimir Oltean
2021-08-08 16:12 ` DENG Qingfang
2021-08-08 21:14 ` Vladimir Oltean
2021-08-10 6:57 ` [RFC net-next 0/3] qca8k bridge flags offload Jonathan McDowell
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=20210807222555.y6r7qxhdyy6d3esx@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=avalentin@vmh.kalnet.hooya.de \
--cc=chunkeey@gmail.com \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=frank-w@public-files.de \
--cc=gururug@gmail.com \
--cc=hannu.nyman@iki.fi \
--cc=john@phrozen.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=nick.lowe@gmail.com \
--cc=nishkadg.linux@gmail.com \
--cc=noodles@earth.li \
--cc=s.l-h@gmx.de \
--cc=vivien.didelot@gmail.com \
--cc=vokac.m@gmail.com \
--cc=xiaofeis@codeaurora.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 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).