From: Stijn Cleynhens <stijncleynhens@gmail.com>
To: "Alvin Šipraga" <alvin.sipraga@analog.com>
Cc: netdev@vger.kernel.org, Linus Walleij <linusw@kernel.org>,
Luiz Angelo Daros de Luca <luizluca@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>,
Mieczyslaw Nalewaj <namiltd@yahoo.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 2/2] net: dsa: realtek: rtl8365mb: keep the neutral PVID in VLAN-unaware bridges
Date: Fri, 6 Nov 2026 16:02:09 +0100 [thread overview]
Message-ID: <20261106150209.3659653-1-stijncleynhens@gmail.com> (raw)
In-Reply-To: <autRCms7HolT2-au@analog.com>
On Wed, Nov 04, 2026 at 04:57:44PM +0100, Alvin Šipraga wrote:
> This part threw me off a bit. What do you mean by "VID of the bridge
> entries"? If the neutral PVID is programmed on the port of a
> VLAN-unaware bridge, I would expect all untagged frames to be classified
> VID=0. And with IVL this should be classified local to the bridge. Is
> that what you want to say, or am I missing something?
Yes, that is what I meant: untagged frames go to VID 0, the VID that DSA
uses for the FDB and MDB entries of a VLAN-unaware bridge. One detail:
it is the per-bridge EFID that keeps the lookup local to the bridge; IVL
makes the VID part of the key. I reworded it in v2.
> Please separate the variables on their own lines.
> I think an else { pvid = 0; } would be more explicit than setting it
> upstairs, but it's a nitpick.
Both done in v2.
> Can we unify _set and _clear somehow? The code gets quite confusing with
> the two variants, and it seems now that with the vlan_filtering
> argument, you can unify the logic.
Agreed. v2 replaces both with rtl8365mb_vlan_pvid_port_commit(), which
takes the target VID (0 for the neutral PVID) and the filtering state,
and is the only place that sets the frame filter, so
rtl8365mb_port_vlan_filtering() no longer touches it. Tested again on an
RTL8367S and an RTL8367S-VB.
Thanks for the review,
Stijn
prev parent reply other threads:[~2026-11-06 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 8:25 [PATCH net 0/2] net: dsa: realtek: rtl8365mb: fix FDB lookups " Stijn Cleynhens
2026-11-04 8:25 ` [PATCH net 1/2] net: dsa: realtek: rtl8365mb: use IVL in VLAN 0 Stijn Cleynhens
2026-11-04 15:22 ` Alvin Šipraga
2026-11-06 15:01 ` Stijn Cleynhens
2026-11-04 8:25 ` [PATCH net 2/2] net: dsa: realtek: rtl8365mb: keep the neutral PVID in VLAN-unaware bridges Stijn Cleynhens
2026-11-04 15:57 ` Alvin Šipraga
2026-11-06 15:02 ` Stijn Cleynhens [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=20261106150209.3659653-1-stijncleynhens@gmail.com \
--to=stijncleynhens@gmail.com \
--cc=alvin.sipraga@analog.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luizluca@gmail.com \
--cc=namiltd@yahoo.com \
--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®