From: Tobias Waldekranz <tobias@waldekranz.com>
To: davem@davemloft.net, kuba@kernel.org
Cc: andrew@lunn.ch, vivien.didelot@gmail.com, f.fainelli@gmail.com,
olteanv@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH v3 net-next 0/8] net: dsa: mv88e6xxx: Offload bridge port flags
Date: Tue, 23 Mar 2021 11:45:03 +0100 [thread overview]
Message-ID: <87im5im9n4.fsf@waldekranz.com> (raw)
In-Reply-To: <20210318192540.895062-1-tobias@waldekranz.com>
On Thu, Mar 18, 2021 at 20:25, Tobias Waldekranz <tobias@waldekranz.com> wrote:
> Add support for offloading learning and broadcast flooding flags. With
> this in place, mv88e6xx supports offloading of all bridge port flags
> that are currently supported by the bridge.
>
> Broadcast flooding is somewhat awkward to control as there is no
> per-port bit for this like there is for unknown unicast and unknown
> multicast. Instead we have to update the ATU entry for the broadcast
> address for all currently used FIDs.
>
> v2 -> v3:
> - Only return a netdev from dsa_port_to_bridge_port if the port is
> currently bridged (Vladimir & Florian)
>
> v1 -> v2:
> - Ensure that mv88e6xxx_vtu_get handles VID 0 (Vladimir)
> - Fixed off-by-one in mv88e6xxx_port_set_assoc_vector (Vladimir)
> - Fast age all entries on port when disabling learning (Vladimir)
> - Correctly detect bridge flags on LAG ports (Vladimir)
>
> Tobias Waldekranz (8):
> net: dsa: Add helper to resolve bridge port from DSA port
> net: dsa: mv88e6xxx: Avoid useless attempts to fast-age LAGs
> net: dsa: mv88e6xxx: Provide generic VTU iterator
> net: dsa: mv88e6xxx: Remove some bureaucracy around querying the VTU
> net: dsa: mv88e6xxx: Use standard helper for broadcast address
> net: dsa: mv88e6xxx: Flood all traffic classes on standalone ports
> net: dsa: mv88e6xxx: Offload bridge learning flag
> net: dsa: mv88e6xxx: Offload bridge broadcast flooding flag
>
> drivers/net/dsa/mv88e6xxx/chip.c | 270 ++++++++++++++++++++++---------
> drivers/net/dsa/mv88e6xxx/port.c | 21 +++
> drivers/net/dsa/mv88e6xxx/port.h | 2 +
> include/net/dsa.h | 14 ++
> net/dsa/dsa_priv.h | 14 +-
> 5 files changed, 232 insertions(+), 89 deletions(-)
>
> --
> 2.25.1
Jakub/Dave, is anything blocking this series from going in? I am unable
to find the series on patchwork, is that why?
next prev parent reply other threads:[~2021-03-23 10:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 19:25 [PATCH v3 net-next 0/8] net: dsa: mv88e6xxx: Offload bridge port flags Tobias Waldekranz
2021-03-18 19:25 ` [PATCH v3 net-next 1/8] net: dsa: Add helper to resolve bridge port from DSA port Tobias Waldekranz
2021-03-18 19:25 ` [PATCH v3 net-next 2/8] net: dsa: mv88e6xxx: Avoid useless attempts to fast-age LAGs Tobias Waldekranz
2021-03-18 19:25 ` [PATCH v3 net-next 3/8] net: dsa: mv88e6xxx: Provide generic VTU iterator Tobias Waldekranz
2021-03-18 19:25 ` [PATCH v3 net-next 4/8] net: dsa: mv88e6xxx: Remove some bureaucracy around querying the VTU Tobias Waldekranz
2021-03-18 19:25 ` [PATCH v3 net-next 5/8] net: dsa: mv88e6xxx: Use standard helper for broadcast address Tobias Waldekranz
2021-03-18 19:25 ` [PATCH v3 net-next 6/8] net: dsa: mv88e6xxx: Flood all traffic classes on standalone ports Tobias Waldekranz
2021-03-18 19:25 ` [PATCH v3 net-next 7/8] net: dsa: mv88e6xxx: Offload bridge learning flag Tobias Waldekranz
2021-03-18 19:25 ` [PATCH v3 net-next 8/8] net: dsa: mv88e6xxx: Offload bridge broadcast flooding flag Tobias Waldekranz
2021-03-23 10:45 ` Tobias Waldekranz [this message]
2021-03-23 10:52 ` [PATCH v3 net-next 0/8] net: dsa: mv88e6xxx: Offload bridge port flags Vladimir Oltean
2021-03-23 11:03 ` Tobias Waldekranz
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=87im5im9n4.fsf@waldekranz.com \
--to=tobias@waldekranz.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--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