From: Jakub Kicinski <kuba@kernel.org>
To: Saeed Mahameed <saeedm@nvidia.com>
Cc: Saeed Mahameed <saeed@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, Eli Cohen <elic@nvidia.com>,
Mark Bloch <mbloch@nvidia.com>
Subject: Re: [net-next 16/16] net/mlx5: Support multiport eswitch mode
Date: Wed, 18 May 2022 21:36:52 -0700 [thread overview]
Message-ID: <20220518213652.312ffb2e@kernel.org> (raw)
In-Reply-To: <20220519042628.e2yqi37ceyks6rbv@sx1>
On Wed, 18 May 2022 21:26:28 -0700 Saeed Mahameed wrote:
> On 18 May 17:21, Jakub Kicinski wrote:
> >On Tue, 17 May 2022 23:49:38 -0700 Saeed Mahameed wrote:
> >> From: Eli Cohen <elic@nvidia.com>
> >>
> >> Multiport eswitch mode is a LAG mode that allows to add rules that
> >> forward traffic to a specific physical port without being affected by LAG
> >> affinity configuration.
> >>
> >> This mode of operation is mutual exclusive with the other LAG modes used
> >> by multipath and bonding.
> >>
> >> To make the transition between the modes, we maintain a counter on the
> >> number of rules specifying one of the uplink representors as the target
> >> of mirred egress redirect action.
> >>
> >> An example of such rule would be:
> >>
> >> $ tc filter add dev enp8s0f0_0 prot all root flower dst_mac \
> >> 00:11:22:33:44:55 action mirred egress redirect dev enp8s0f0
> >>
> >> If the reference count just grows to one and LAG is not in use, we
> >> create the LAG in multiport eswitch mode. Other mode changes are not
> >> allowed while in this mode. When the reference count reaches zero, we
> >> destroy the LAG and let other modes be used if needed.
> >>
> >> logic also changed such that if forwarding to some uplink destination
> >> cannot be guaranteed, we fail the operation so the rule will eventually
> >> be in software and not in hardware.
> >>
> >> Signed-off-by: Eli Cohen <elic@nvidia.com>
> >> Reviewed-by: Mark Bloch <mbloch@nvidia.com>
> >> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
> >
> >GCC 12 also points out that:
> >
> >drivers/net/ethernet/mellanox/mlx5/core/lag/lag.c: In function ‘mlx5_do_bond’:
> >drivers/net/ethernet/mellanox/mlx5/core/lag/lag.c:786:28: warning: ‘tracker’ is used uninitialized [-Wuninitialized]
> > 786 | struct lag_tracker tracker;
> > | ^~~~~~~
> >drivers/net/ethernet/mellanox/mlx5/core/lag/lag.c:786:28: note: ‘tracker’ declared here
> > 786 | struct lag_tracker tracker;
> > | ^~~~~~~
>
> it's a false alarm, anyway clang and gcc12 are happy on my machine:
Yeah, looks like a false alarm.
> $ KCFLAGS="-Wall" make W=1 drivers/net/ethernet/mellanox/mlx5/core/lag/lag.o
No extra flags, basic allmodconfig build here (well, with WERROR=n).
> CALL scripts/checksyscalls.sh
> CALL scripts/atomic/check-atomics.sh
> DESCEND objtool
> CC drivers/net/ethernet/mellanox/mlx5/core/lag/lag.o
>
> $ gcc --version
> gcc (GCC) 12.1.1 20220507 (Red Hat 12.1.1-1)
Same:
gcc (GCC) 12.1.1 20220507 (Red Hat 12.1.1-1)
prev parent reply other threads:[~2022-05-19 4:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 6:49 [pull request][net-next 00/16] mlx5 updates 2022-05-17 Saeed Mahameed
2022-05-18 6:49 ` [net-next 01/16] net/mlx5: sparse: error: context imbalance in 'mlx5_vf_get_core_dev' Saeed Mahameed
2022-05-18 11:10 ` patchwork-bot+netdevbpf
2022-05-18 6:49 ` [net-next 02/16] net/mlx5: Add last command failure syndrome to debugfs Saeed Mahameed
2022-05-18 6:49 ` [net-next 03/16] net/mlx5: Inline db alloc API function Saeed Mahameed
2022-05-18 6:49 ` [net-next 04/16] net/mlx5: Allocate virtually contiguous memory in vport.c Saeed Mahameed
2022-05-18 6:49 ` [net-next 05/16] net/mlx5: Allocate virtually contiguous memory in pci_irq.c Saeed Mahameed
2022-05-18 6:49 ` [net-next 06/16] net/mlx5e: Allocate virtually contiguous memory for VLANs list Saeed Mahameed
2022-05-18 6:49 ` [net-next 07/16] net/mlx5e: Allocate virtually contiguous memory for reps structures Saeed Mahameed
2022-05-18 6:49 ` [net-next 08/16] net/mlx5e: IPoIB, Improve ethtool rxnfc callback structure in IPoIB Saeed Mahameed
2022-05-18 6:49 ` [net-next 09/16] net/mlx5e: Support partial GSO for tunnels over vlans Saeed Mahameed
2022-05-18 6:49 ` [net-next 10/16] net/mlx5e: Allow relaxed ordering over VFs Saeed Mahameed
2022-05-18 6:49 ` [net-next 11/16] net/mlx5e: CT: Add ct driver counters Saeed Mahameed
2022-05-18 6:49 ` [net-next 12/16] net/mlx5e: Correct the calculation of max channels for rep Saeed Mahameed
2022-05-18 6:49 ` [net-next 13/16] net/mlx5e: Add XDP SQs to uplink representors steering tables Saeed Mahameed
2022-05-18 6:49 ` [net-next 14/16] net/mlx5: Lag, refactor lag state machine Saeed Mahameed
2022-05-18 6:49 ` [net-next 15/16] net/mlx5: Remove unused argument Saeed Mahameed
2022-05-18 6:49 ` [net-next 16/16] net/mlx5: Support multiport eswitch mode Saeed Mahameed
2022-05-19 0:21 ` Jakub Kicinski
2022-05-19 4:26 ` Saeed Mahameed
2022-05-19 4:36 ` Jakub Kicinski [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=20220518213652.312ffb2e@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=elic@nvidia.com \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@kernel.org \
--cc=saeedm@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).