From: David Yang <mmyangfl@gmail.com>
To: netdev@vger.kernel.org
Cc: David Yang <mmyangfl@gmail.com>, Andrew Lunn <andrew@lunn.ch>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH net-next v3 0/3] net: dsa: motorcomm: Add BR_FLOOD and BR_MCAST_FLOOD support
Date: Tue, 3 Nov 2026 22:01:04 +0800 [thread overview]
Message-ID: <20261103140109.874443-1-mmyangfl@gmail.com> (raw)
Offload BR_FLOOD / BR_MCAST_FLOOD to the hardware for bridges when
feasible.
v3:
- refactor port isolation and filter action for standalone ports
- recompute flags when a port leaves bridge
- honor BR_HAIRPIN
v2: https://lore.kernel.org/r/20261011030228.2761810-1-mmyangfl@gmail.com
- fix build error
v1: https://lore.kernel.org/r/20261009005542.72860-1-mmyangfl@gmail.com
David Yang (3):
net: dsa: motorcomm: Isolate all ports during chip setup
net: dsa: motorcomm: Rely on port isolation for CPU port
net: dsa: motorcomm: Add BR_FLOOD and BR_MCAST_FLOOD support
drivers/net/dsa/motorcomm/chip.c | 233 +++++++++++++++++++++----------
drivers/net/dsa/motorcomm/chip.h | 4 +
2 files changed, 164 insertions(+), 73 deletions(-)
--
2.53.0
next reply other threads:[~2026-11-03 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 14:01 David Yang [this message]
2026-11-03 14:01 ` [PATCH net-next v3 1/3] net: dsa: motorcomm: Isolate all ports during chip setup David Yang
2026-11-03 14:01 ` [PATCH net-next v3 2/3] net: dsa: motorcomm: Rely on port isolation for CPU port David Yang
2026-11-03 14:01 ` [PATCH net-next v3 3/3] net: dsa: motorcomm: Add BR_FLOOD and BR_MCAST_FLOOD support David Yang
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=20261103140109.874443-1-mmyangfl@gmail.com \
--to=mmyangfl@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®