From: Ido Schimmel <idosch@nvidia.com>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Petr Machata <petrm@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Ivan Vecera <ivecera@redhat.com>,
netdev@vger.kernel.org, Nikolay Aleksandrov <razor@blackwall.org>,
Roopa Prabhu <roopa@nvidia.com>, Jiri Pirko <jiri@nvidia.com>,
bridge@lists.linux-foundation.org,
"Hans J . Schultz" <netdev@kapio-technology.com>,
mlxsw@nvidia.com
Subject: Re: [PATCH net-next 11/15] mlxsw: spectrum_switchdev: Add locked bridge port support
Date: Wed, 9 Nov 2022 10:26:29 +0200 [thread overview]
Message-ID: <Y2tkNa7nnAdeD5Nc@shredder> (raw)
In-Reply-To: <20221108145929.qmu2gvd5vvgvasyy@skbuf>
On Tue, Nov 08, 2022 at 04:59:29PM +0200, Vladimir Oltean wrote:
> Can't really figure out from the patch, sorry. Port security works with
> LAG offload?
Yes. It's just that port security needs to be enabled on each of the
member ports. FDB entries that point to a LAG are programmed with a
lag_id. When a packet is received from a LAG the hardware will compare
source_lag_id == lag_id instead of rx_local_port == tx_local_port.
next prev parent reply other threads:[~2022-11-09 8:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 10:47 [PATCH net-next 00/15] mlxsw: Add 802.1X and MAB offload support Petr Machata
2022-11-08 10:47 ` [PATCH net-next 01/15] bridge: switchdev: Let device drivers determine FDB offload indication Petr Machata
2022-11-08 14:16 ` Vladimir Oltean
2022-11-08 18:01 ` Nikolay Aleksandrov
2022-11-08 10:47 ` [PATCH net-next 02/15] bridge: switchdev: Allow device drivers to install locked FDB entries Petr Machata
2022-11-08 14:21 ` Vladimir Oltean
2022-11-08 18:01 ` Nikolay Aleksandrov
2022-11-08 10:47 ` [PATCH net-next 03/15] bridge: switchdev: Reflect MAB bridge port flag to device drivers Petr Machata
2022-11-08 14:22 ` Vladimir Oltean
2022-11-08 18:02 ` Nikolay Aleksandrov
2022-11-08 10:47 ` [PATCH net-next 04/15] devlink: Add packet traps for 802.1X operation Petr Machata
2022-11-08 14:38 ` Vladimir Oltean
2022-11-08 10:47 ` [PATCH net-next 05/15] mlxsw: spectrum_trap: Register 802.1X packet traps with devlink Petr Machata
2022-11-08 10:47 ` [PATCH net-next 06/15] mlxsw: reg: Add Switch Port FDB Security Register Petr Machata
2022-11-08 10:47 ` [PATCH net-next 07/15] mlxsw: spectrum: Add an API to configure security checks Petr Machata
2022-11-08 10:47 ` [PATCH net-next 08/15] mlxsw: spectrum_switchdev: Prepare for locked FDB notifications Petr Machata
2022-11-08 10:47 ` [PATCH net-next 09/15] mlxsw: spectrum_switchdev: Add support " Petr Machata
2022-11-08 10:47 ` [PATCH net-next 10/15] mlxsw: spectrum_switchdev: Use extack in bridge port flag validation Petr Machata
2022-11-08 10:47 ` [PATCH net-next 11/15] mlxsw: spectrum_switchdev: Add locked bridge port support Petr Machata
2022-11-08 14:59 ` Vladimir Oltean
2022-11-09 8:26 ` Ido Schimmel [this message]
2022-11-09 9:21 ` Vladimir Oltean
2022-11-08 10:47 ` [PATCH net-next 12/15] selftests: devlink_lib: Split out helper Petr Machata
2022-11-08 10:47 ` [PATCH net-next 13/15] selftests: mlxsw: Add a test for EAPOL trap Petr Machata
2022-11-08 15:11 ` Vladimir Oltean
2022-11-08 10:47 ` [PATCH net-next 14/15] selftests: mlxsw: Add a test for locked port trap Petr Machata
2022-11-08 15:30 ` Vladimir Oltean
2022-11-08 10:47 ` [PATCH net-next 15/15] selftests: mlxsw: Add a test for invalid locked bridge port configurations Petr Machata
2022-11-08 14:42 ` Vladimir Oltean
2022-11-08 10:59 ` [PATCH net-next 00/15] mlxsw: Add 802.1X and MAB offload support Ido Schimmel
2022-11-08 15:31 ` Vladimir Oltean
2022-11-10 3:30 ` patchwork-bot+netdevbpf
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=Y2tkNa7nnAdeD5Nc@shredder \
--to=idosch@nvidia.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ivecera@redhat.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@kapio-technology.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.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;
as well as URLs for NNTP newsgroup(s).