From: Vladimir Oltean <olteanv@gmail.com>
To: Kurt Kanzenbach <kurt@kmk-computers.de>
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>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: dsa: hellcreek: Offload bridge port flags
Date: Mon, 15 Mar 2021 23:34:13 +0200 [thread overview]
Message-ID: <20210315213413.k4td2urqxl2sqflg@skbuf> (raw)
In-Reply-To: <87lfao88d3.fsf@kmk-computers.de>
On Mon, Mar 15, 2021 at 09:33:44PM +0100, Kurt Kanzenbach wrote:
> On Mon Mar 15 2021, Vladimir Oltean wrote:
> > On Sun, Mar 14, 2021 at 01:52:08PM +0100, Kurt Kanzenbach wrote:
> >> + if (enable)
> >> + val &= ~HR_PTCFG_UUC_FLT;
> >> + else
> >> + val |= HR_PTCFG_UUC_FLT;
> >
> > What does 'unknown unicast filtering' mean/do, exactly?
> > The semantics of BR_FLOOD are on egress: all unicast packets with an
> > unknown destination that are received on ports from this bridging domain
> > can be flooded towards port X if that port has flooding enabled.
> > When I hear "filtering", I imagine an ingress setting, am I wrong?
>
> It means that frames without matching fdb entries towards this port are
> discarded.
The phrasing is still not crystal clear, sorry.
You have a switch with 2 user ports, lan0 and lan1, and one CPU port.
lan0 and lan1 are under br0. lan0 has 'unknown unicast filtering'
disabled, lan1 has it enabled, and the CPU port has it disabled.
You receive a packet from lan0 towards an unknown unicast destination.
Is the packet discarded or is it sent to the CPU port?
next prev parent reply other threads:[~2021-03-15 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 12:52 [PATCH net-next] net: dsa: hellcreek: Offload bridge port flags Kurt Kanzenbach
2021-03-14 13:43 ` Leon Romanovsky
2021-03-15 19:40 ` patchwork-bot+netdevbpf
2021-03-15 20:08 ` Vladimir Oltean
2021-03-15 20:33 ` Kurt Kanzenbach
2021-03-15 21:34 ` Vladimir Oltean [this message]
2021-03-16 8:38 ` Kurt Kanzenbach
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=20210315213413.k4td2urqxl2sqflg@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=kurt@kmk-computers.de \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.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