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:11:00 +0000 [thread overview]
Message-ID: <DM4PR12MB845219F7A6B5ADC7E5831DBDA4C32@DM4PR12MB8452.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20250225120213.2968616-2-ophirmu@nvidia.com>
> -----Original Message-----
> From: Ophir Munk <ophirmu@nvidia.com>
> Sent: Tuesday, February 25, 2025 13:02
> To: Dariusz Sosnowski <dsosnowski@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; Raslan Darawsheh <rasland@nvidia.com>
> Subject: [PATCH V1 2/4] net/mlx5: support FDB unified domain
>
> Legacy FDB domain is enhanced with optional three sub-domains: FDB_RX
> FDB_TX and FDB_UNIFIED. Based on FW capability bit mlx5 will work in either
> legacy or unified mode. To work in fdb unified mode the flow attribute transfer
> bit must be set and the fdb sub domains are determined by the table specialize
> flags SPECIALIZE_TRANSFER_WIRE_ORIG and
> SPECIALIZE_TRANSFER_VPORT_ORIG.
>
> +------------+-------------+--------------+
> | WIRE_ORIG | VPORT_ORIG | FDB domain |
> +------------+-------------+--------------+
> | 0 | 0 | FDB_UNIFIED |
> | 0 | 1 | FDB_TX |
> | 1 | 0 | FDB_RX |
> +------------+-------------+--------------+
>
> There can be no two groups which only differ in their fdb sub domain.
> A table must be created in a group which has the same fdb sub domain.
>
> Signed-off-by: Ophir Munk <ophirmu@nvidia.com>
Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
Best regards,
Dariusz Sosnowski
next prev parent reply other threads:[~2025-02-25 12:11 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 [this message]
2025-02-25 12:21 ` Dariusz Sosnowski
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=DM4PR12MB845219F7A6B5ADC7E5831DBDA4C32@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).