From: Raslan Darawsheh <rasland@nvidia.com>
To: Michael Baum <michaelba@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>, Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: RE: [PATCH 0/2] net/mlx5: add modify MPLS support
Date: Thu, 22 Jun 2023 08:29:10 +0000 [thread overview]
Message-ID: <BYAPR12MB3078A5F1CCB5D9DD8B649AFFCF22A@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230614055234.2322466-1-michaelba@nvidia.com>
Hi,
> -----Original Message-----
> From: Michael Baum <michaelba@nvidia.com>
> Sent: Wednesday, June 14, 2023 8:53 AM
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@nvidia.com>; Raslan Darawsheh
> <rasland@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>
> Subject: [PATCH 0/2] net/mlx5: add modify MPLS support
>
> Add support for MPLS header modification.
>
> RFC:
> https://patchwork.dpdk.org/project/dpdk/patch/20230420094347.523784
> -1-michaelba@nvidia.com/
>
> Michael Baum (2):
> net/mlx5: align implementation with modify API
> net/mlx5: add MPLS modify field support
>
> doc/guides/nics/mlx5.rst | 2 ++
> drivers/common/mlx5/mlx5_prm.h | 5 +++
> drivers/net/mlx5/mlx5_flow.h | 13 ++++++++
> drivers/net/mlx5/mlx5_flow_dv.c | 41 ++++++++++++++++++++++++
> drivers/net/mlx5/mlx5_flow_hw.c | 57 +++++++++++++++++++++++++------
> --
> 5 files changed, 105 insertions(+), 13 deletions(-)
>
> --
> 2.25.1
Series applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2023-06-22 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 5:52 Michael Baum
2023-06-14 5:52 ` [PATCH 1/2] net/mlx5: align implementation with modify API Michael Baum
2023-06-14 5:52 ` [PATCH 2/2] net/mlx5: add MPLS modify field support Michael Baum
2023-06-22 8:29 ` 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=BYAPR12MB3078A5F1CCB5D9DD8B649AFFCF22A@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=michaelba@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).