From: Andrew Lunn <andrew@lunn.ch>
To: Pavel Machek <pavel@ucw.cz>
Cc: Anderson Luiz Alves <alacn1@gmail.com>,
vivien.didelot@savoirfairelinux.com, f.fainelli@gmail.com,
davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 net] mv88e6060: disable hardware level MAC learning
Date: Fri, 28 Dec 2018 10:06:30 +0100 [thread overview]
Message-ID: <20181228090630.GB31460@lunn.ch> (raw)
In-Reply-To: <20181228082255.GB6341@amd>
On Fri, Dec 28, 2018 at 09:22:55AM +0100, Pavel Machek wrote:
> On Fri 2018-11-30 21:58:36, Anderson Luiz Alves wrote:
> > Disable hardware level MAC learning because it breaks station roaming.
> > When enabled it drops all frames that arrive from a MAC address
> > that is on a different port at learning table.
> >
> > Signed-off-by: Anderson Luiz Alves <alacn1@gmail.com>
>
> Will not this effectively disable the hardware switching leading to
> serious performance implications?
Hi Pavel
This switch is not doing hardware switching to start with. See
mv88e6060_setup_port():
/* Port based VLAN map: give each port its own address
* database, allow the CPU port to talk to each of the 'real'
* ports, and allow each of the 'real' ports to only talk to
* the CPU port.
*/
REG_WRITE(addr, PORT_VLAN_MAP,
((p & 0xf) << PORT_VLAN_MAP_DBNUM_SHIFT) |
(dsa_is_cpu_port(ds, p) ? dsa_user_ports(ds) :
BIT(dsa_to_port(ds, p)->cpu_dp->index)));
/* Port Association Vector: when learning source addresses
* of packets, add the address to the address database using
* a port bitmap that has only the bit for this port set and
* the other bits clear.
*/
REG_WRITE(addr, PORT_ASSOC_VECTOR, BIT(p));
This is a very old driver, added way before offload support was added.
Andrew
prev parent reply other threads:[~2018-12-28 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 23:58 [PATCH v3 net] mv88e6060: disable hardware level MAC learning Anderson Luiz Alves
2018-12-01 15:39 ` Andrew Lunn
2018-12-04 0:04 ` David Miller
2018-12-28 8:22 ` Pavel Machek
2018-12-28 9:06 ` Andrew Lunn [this message]
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=20181228090630.GB31460@lunn.ch \
--to=andrew@lunn.ch \
--cc=alacn1@gmail.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
--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).