From: David Miller <davem@davemloft.net>
To: olteanv@gmail.com
Cc: vivien.didelot@gmail.com, netdev@vger.kernel.org,
f.fainelli@gmail.com, andrew@lunn.ch
Subject: Re: [PATCH net-next v2 0/6] net: dsa: explicit programmation of VLAN on CPU ports
Date: Tue, 27 Aug 2019 20:17:53 -0700 (PDT) [thread overview]
Message-ID: <20190827.201753.619474113830630076.davem@davemloft.net> (raw)
In-Reply-To: <CA+h21hqPTqzCPPYqF1zvbGhu=yeqPFQ_X77xtfmt1mzENDQ9Dw@mail.gmail.com>
From: Vladimir Oltean <olteanv@gmail.com>
Date: Sun, 25 Aug 2019 21:27:23 +0300
> On Sun, 25 Aug 2019 at 20:25, Vivien Didelot <vivien.didelot@gmail.com> wrote:
>>
>> When a VLAN is programmed on a user port, every switch of the fabric also
>> program the CPU ports and the DSA links as part of the VLAN. To do that,
>> DSA makes use of bitmaps to prepare all members of a VLAN.
>>
>> While this is expected for DSA links which are used as conduit between
>> interconnected switches, only the dedicated CPU port of the slave must be
>> programmed, not all CPU ports of the fabric. This may also cause problems in
>> other corners of DSA such as the tag_8021q.c driver, which needs to program
>> its ports manually, CPU port included.
>>
>> We need the dsa_port_vlan_{add,del} functions and its dsa_port_vid_{add,del}
>> variants to simply trigger the VLAN programmation without any logic in them,
>> but they may currently skip the operation based on the bridge device state.
>>
>> This patchset gets rid of the bitmap operations, and moves the bridge device
>> check as well as the explicit programmation of CPU ports where they belong,
>> in the slave code.
>>
>> While at it, clear the VLAN flags before programming a CPU port, as it
>> doesn't make sense to forward the PVID flag for example for such ports.
>>
>> Changes in v2: only clear the PVID flag.
...
> For the whole series:
> Tested-by: Vladimir Oltean <olteanv@gmail.com>
> Thanks!
Series applied.
prev parent reply other threads:[~2019-08-28 3:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-25 17:25 [PATCH net-next v2 0/6] net: dsa: explicit programmation of VLAN on CPU ports Vivien Didelot
2019-08-25 17:25 ` [PATCH net-next v2 1/6] net: dsa: remove bitmap operations Vivien Didelot
2019-08-25 17:25 ` [PATCH net-next v2 2/6] net: dsa: do not skip -EOPNOTSUPP in dsa_port_vid_add Vivien Didelot
2019-08-25 17:25 ` [PATCH net-next v2 3/6] net: dsa: add slave VLAN helpers Vivien Didelot
2019-08-25 17:25 ` [PATCH net-next v2 4/6] net: dsa: check bridge VLAN in slave operations Vivien Didelot
2019-08-25 17:25 ` [PATCH net-next v2 5/6] net: dsa: program VLAN on CPU port from slave Vivien Didelot
2019-08-25 17:25 ` [PATCH net-next v2 6/6] net: dsa: clear VLAN PVID flag for CPU port Vivien Didelot
2019-08-25 18:27 ` [PATCH net-next v2 0/6] net: dsa: explicit programmation of VLAN on CPU ports Vladimir Oltean
2019-08-28 3:17 ` David Miller [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=20190827.201753.619474113830630076.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--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