From: Jakub Kicinski <kuba@kernel.org>
To: Saeed Mahameed <saeed@kernel.org>
Cc: Tariq Toukan <tariqt@nvidia.com>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Saeed Mahameed <saeedm@nvidia.com>,
Mark Bloch <mbloch@nvidia.com>, Leon Romanovsky <leon@kernel.org>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org, Gal Pressman <gal@nvidia.com>,
Moshe Shemesh <moshe@nvidia.com>,
Dragos Tatulea <dtatulea@nvidia.com>
Subject: Re: [PATCH net-next] net/mlx5e: Enable mac forwarding on uplink representor
Date: Wed, 18 Mar 2026 16:44:00 -0700 [thread overview]
Message-ID: <20260318164400.11f75f41@kernel.org> (raw)
In-Reply-To: <abr4O7rfDoOIKHYW@sx113>
On Wed, 18 Mar 2026 12:10:37 -0700 Saeed Mahameed wrote:
> >> Mac forwarding in the sense of linux bridge mac forwarding mechanism which
> >> requires set_rx_mode ndo to be implemented.
> >>
> >> Linux-bridge --> mlx5-uplink-rep --> set_rx_mode --> set up mac in HW.
> >
> >And the actual forwarding happens in SW bridge? This is just to
> >configure the Rx filter not to discard on Rx?
>
> Yes Forwarding happens on the SW bridge, just to register the mac so it
> won't get dropped.
Ah! Please respin with a better explanation and calling that out?
I think it's fair for the reader to assume offload when reading
about representors.
prev parent reply other threads:[~2026-03-18 23:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 10:48 [PATCH net-next] net/mlx5e: Enable mac forwarding on uplink representor Tariq Toukan
2026-03-12 3:33 ` Jakub Kicinski
2026-03-17 18:12 ` Saeed Mahameed
2026-03-17 21:36 ` Jakub Kicinski
2026-03-18 19:10 ` Saeed Mahameed
2026-03-18 23:44 ` 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=20260318164400.11f75f41@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@kernel.org \
--cc=saeedm@nvidia.com \
--cc=tariqt@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