From: Raslan Darawsheh <rasland@nvidia.com>
To: Gavin Li <gavinl@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Ori Kam <orika@nvidia.com>, Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Cc: "Jiawei(Jonny) Wang" <jiaweiw@nvidia.com>
Subject: RE: [V1 0/2] use traffic class PRM field for IPv6 modification
Date: Wed, 17 Jan 2024 13:41:44 +0000 [thread overview]
Message-ID: <MN0PR12MB605658864F3E4751FD7E0B60CF722@MN0PR12MB6056.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240112075055.1288263-1-gavinl@nvidia.com>
Hi,
> -----Original Message-----
> From: Gavin Li <gavinl@nvidia.com>
> Sent: Friday, January 12, 2024 9:51 AM
> To: dev@dpdk.org; Dariusz Sosnowski <dsosnowski@nvidia.com>; Slava
> Ovsiienko <viacheslavo@nvidia.com>; Ori Kam <orika@nvidia.com>;
> Suanming Mou <suanmingm@nvidia.com>; Matan Azrad
> <matan@nvidia.com>
> Cc: Jiawei(Jonny) Wang <jiaweiw@nvidia.com>; Raslan Darawsheh
> <rasland@nvidia.com>
> Subject: [V1 0/2] use traffic class PRM field for IPv6 modification
>
> New field ID OUT_IPV6_TRAFFIC_CLASS for IPv6 was defined and will be used
> by both IPv6 ECN and DSCP.
>
> To apply the new ID and keep backward compatibility with different RDMA
> core and FW releases
> 1) detect the support of the new ID in RDMA core and FW.
> 2) apply the new ID if possible otherwise, keep using the old ID.
>
> Gavin Li (2):
> net/mlx5: discover IPv6 traffic class support in RDMA core
> net/mlx5: use traffic class PRM field for IPv6 modification
>
> drivers/common/mlx5/mlx5_devx_cmds.c | 3 ++
> drivers/common/mlx5/mlx5_devx_cmds.h | 1 +
> drivers/common/mlx5/mlx5_prm.h | 8 ++-
> drivers/net/mlx5/linux/mlx5_os.c | 5 ++
> drivers/net/mlx5/mlx5.h | 1 +
> drivers/net/mlx5/mlx5_flow.c | 42 +++++++++++++++
> drivers/net/mlx5/mlx5_flow.h | 4 ++
> drivers/net/mlx5/mlx5_flow_dv.c | 78 ++++++++++++++++++++++++----
> drivers/net/mlx5/mlx5_flow_hw.c | 7 +++
> 9 files changed, 138 insertions(+), 11 deletions(-)
>
> --
> 2.39.1
Series applied to next-net-mlx
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2024-01-17 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 7:50 Gavin Li
2024-01-12 7:50 ` [V1 1/2] net/mlx5: discover IPv6 traffic class support in RDMA core Gavin Li
2024-01-12 7:50 ` [V1 2/2] net/mlx5: use traffic class PRM field for IPv6 modification Gavin Li
2024-01-17 13:41 ` Raslan Darawsheh [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=MN0PR12MB605658864F3E4751FD7E0B60CF722@MN0PR12MB6056.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=gavinl@nvidia.com \
--cc=jiaweiw@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@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).