From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: Ophir Munk <ophirmu@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Raslan Darawsheh <rasland@nvidia.com>
Subject: RE: [PATCH V1 2/4] net/mlx5: support FDB unified domain
Date: Tue, 25 Feb 2025 12:21:00 +0000 [thread overview]
Message-ID: <DM4PR12MB8452B9927551003EEA379A81A4C32@DM4PR12MB8452.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20250225120213.2968616-2-ophirmu@nvidia.com>
Nacked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
Please see below:
> diff --git a/drivers/net/mlx5/linux/mlx5_os.c b/drivers/net/mlx5/linux/mlx5_os.c
> index 091f288..9410211 100644
> --- a/drivers/net/mlx5/linux/mlx5_os.c
> +++ b/drivers/net/mlx5/linux/mlx5_os.c
> @@ -1707,6 +1707,17 @@ mlx5_dev_spawn(struct rte_device *dpdk_dev,
> LIST_INIT(&priv->hw_ext_ctrl_flows);
> if (priv->sh->config.dv_flow_en == 2) { #ifdef
> HAVE_MLX5_HWS_SUPPORT
> + /*
> + * Unified FDB flag is only needed for the actions created on
> the transfer
> + * port. proxy port. It is not needed on the following ports:
> + * 1. NIC PF / VF / SF
> + * 2. in Verbs or DV/DR mode
> + * 3. with unsupported FW
> + * 4. all representors in HWS
> + */
> + priv->unified_fdb_en = !!priv->master;
This should be also based on FW capability check introduced in previous commit.
> + DRV_LOG(DEBUG, "port %u: unified FDB %s enabled.",
> + eth_dev->data->port_id, priv->unified_fdb_en ? "is" :
> "isn't");
> if (priv->sh->config.dv_esw_en) {
> uint32_t usable_bits;
> uint32_t required_bits;
next prev parent reply other threads:[~2025-02-25 12:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 12:02 [PATCH V1 1/4] common/mlx5: support FDB unified capability query Ophir Munk
2025-02-25 12:02 ` [PATCH V1 2/4] net/mlx5: support FDB unified domain Ophir Munk
2025-02-25 12:11 ` Dariusz Sosnowski
2025-02-25 12:21 ` Dariusz Sosnowski [this message]
2025-02-25 12:02 ` [PATCH V1 3/4] net/mlx5: remove unneeded FDB flag on representor action Ophir Munk
2025-02-25 12:11 ` Dariusz Sosnowski
2025-02-25 12:02 ` [PATCH V1 4/4] net/mlx5/hws: allow different types in miss validation Ophir Munk
2025-02-25 12:11 ` Dariusz Sosnowski
2025-02-25 12:10 ` [PATCH V1 1/4] common/mlx5: support FDB unified capability query Dariusz Sosnowski
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=DM4PR12MB8452B9927551003EEA379A81A4C32@DM4PR12MB8452.namprd12.prod.outlook.com \
--to=dsosnowski@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=ophirmu@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@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).