From: Vladimir Oltean <olteanv@gmail.com>
To: Aaron Thompson <dev@aaront.org>
Cc: Tobias Waldekranz <tobias@waldekranz.com>, netdev@vger.kernel.org
Subject: Re: mv88e6xxx assisted learning on CPU port
Date: Sun, 22 Jan 2023 15:10:58 +0200 [thread overview]
Message-ID: <20230122131058.n4b2jejecksane3j@skbuf> (raw)
In-Reply-To: <01000185d7afea8b-cdad9c75-b82b-456e-80c1-ce62d6afe761-000000@email.amazonses.com>
On Sun, Jan 22, 2023 at 04:15:08AM +0000, Aaron Thompson wrote:
> Hi Tobias, Vladimir, et al.,
>
> Just a quick question: Is there a reason why the patch to enable
> assisted_learning_on_cpu_port for mv88e6xxx never made it to mainline? It
> was included in this RFC series:
>
> https://lore.kernel.org/all/20210224114350.2791260-14-olteanv@gmail.com/
>
> But not in the series that eventually made it to mainline. In my searching
> on lore, I haven't been able to find anything else about it, yea or nay.
>
> Thanks,
> -- Aaron
Because since commit ce5df6894a57 ("net: dsa: mv88e6xxx: map virtual
bridges with forwarding offload in the PVT"), the mv88e6xxx driver
supports a more potent feature (bridge TX forwarding offload), which
sends packets from software to the switch in a way in which the switch
can automatically learn their MAC SA + VLAN ID, among other benefits.
More details can be found here:
https://www.kernel.org/doc/html/latest/networking/dsa/dsa.html#bridge-layer
prev parent reply other threads:[~2023-01-22 13:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 4:15 mv88e6xxx assisted learning on CPU port Aaron Thompson
2023-01-22 13:10 ` Vladimir Oltean [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=20230122131058.n4b2jejecksane3j@skbuf \
--to=olteanv@gmail.com \
--cc=dev@aaront.org \
--cc=netdev@vger.kernel.org \
--cc=tobias@waldekranz.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