public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Nikolay Aleksandrov <nikolay@nvidia.com>,
	"stephen@networkplumber.org" <stephen@networkplumber.org>,
	"olteanv@gmail.com" <olteanv@gmail.com>,
	Roopa Prabhu <roopa@nvidia.com>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"davem@davemloft.net" <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"andrew@lunn.ch" <andrew@lunn.ch>
Subject: Re: [PATCH net-next] net: bridge: pop vlan from skb if filtering is disabled but it's a pvid
Date: Mon, 21 Sep 2020 12:44:43 -0700	[thread overview]
Message-ID: <a322976c-6d47-aae8-32eb-3593f8e3cc10@gmail.com> (raw)
In-Reply-To: <cc20face-ec67-d444-1cf8-f4257dbe1e1c@gmail.com>

On 9/14/20 1:11 PM, Florian Fainelli wrote:
>> Less important, but still:
>>   - it is in the fast path for everyone
>>   - it can already be fixed by a tc action/8021q device
> 
> Sure, but the point is that it should be fixed in a way that is
> transparent to the user, as much as possible.
> 
>>
>> We can go into details but that would be a waste of time, instead I
>> think we
>> should focus on Vladimir's proposed DSA change.
>>
>> Vladimir, I think with the right pvid helper the patch would reduce to
>> dsa_untag_bridge_pvid() on the Rx path only. One thing that I'm
>> curious about
>> is shouldn't dsa_untag_bridge_pvid() check if the bridge pvid is == to
>> the skb
>> tag and the port's pvid?
>> Since we can have the port's pvid different from the bridge's. That's
>> for the
>> case of vlan_filtering=1 and the port having that vlan, but not as pvid.

Vladimir, let me know if you have a patch for DSA and I can give it a
try quickly. Thanks!
-- 
Florian

  reply	other threads:[~2020-09-21 19:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-11 23:16 [PATCH net-next] net: bridge: pop vlan from skb if filtering is disabled but it's a pvid Vladimir Oltean
2020-09-12  6:56 ` Nikolay Aleksandrov
2020-09-12  7:23   ` Vladimir Oltean
2020-09-12  7:37     ` Nikolay Aleksandrov
2020-09-12  7:50       ` Vladimir Oltean
2020-09-12 19:38   ` Florian Fainelli
2020-09-14  7:51     ` Nikolay Aleksandrov
2020-09-14 20:11       ` Florian Fainelli
2020-09-21 19:44         ` Florian Fainelli [this message]
2020-09-21 19:56           ` Vladimir Oltean
2020-09-21 22:12             ` Vladimir Oltean

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=a322976c-6d47-aae8-32eb-3593f8e3cc10@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@nvidia.com \
    --cc=olteanv@gmail.com \
    --cc=roopa@nvidia.com \
    --cc=stephen@networkplumber.org \
    /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