From: Suanming Mou <suanmingm@nvidia.com>
To: Michael Baum <michaelba@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>,
Raslan Darawsheh <rasland@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Ori Kam <orika@nvidia.com>
Subject: RE: [PATCH v3 2/2] net/mlx5: add MPLS tunnel support for HWS
Date: Wed, 8 Mar 2023 03:34:36 +0000 [thread overview]
Message-ID: <CO6PR12MB53961D3E9FEE8129E5331316C1B49@CO6PR12MB5396.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230223074734.3315320-3-michaelba@nvidia.com>
> -----Original Message-----
> From: Michael Baum <michaelba@nvidia.com>
> Sent: Thursday, February 23, 2023 3:48 PM
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@nvidia.com>; Raslan Darawsheh
> <rasland@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>; Ori Kam
> <orika@nvidia.com>
> Subject: [PATCH v3 2/2] net/mlx5: add MPLS tunnel support for HWS
>
> Add support for MPLS tunnel item in HWS.
>
> Signed-off-by: Michael Baum <michaelba@nvidia.com>
> Acked-by: Ori Kam <orika@nvidia.com>
Acked-by: Suanming Mou <suanmingm@nvidia.com>
next prev parent reply other threads:[~2023-03-08 3:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 21:23 [PATCH v2 0/2] net/mlx5: support MPLSoUDP " Michael Baum
2023-02-22 21:23 ` [PATCH v2 1/2] net/mlx5/hws: support matching on MPLSoUDP Michael Baum
2023-02-22 21:23 ` [PATCH v2 2/2] net/mlx5: add MPLS tunnel support for HWS Michael Baum
2023-02-23 7:47 ` [PATCH v3 0/2] net/mlx5: support MPLSoUDP " Michael Baum
2023-02-23 7:47 ` [PATCH v3 1/2] net/mlx5/hws: support matching on MPLSoUDP Michael Baum
2023-03-07 12:41 ` Slava Ovsiienko
2023-02-23 7:47 ` [PATCH v3 2/2] net/mlx5: add MPLS tunnel support for HWS Michael Baum
2023-03-08 3:34 ` Suanming Mou [this message]
2023-03-08 13:51 ` [PATCH v3 0/2] net/mlx5: support MPLSoUDP " Raslan Darawsheh
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=CO6PR12MB53961D3E9FEE8129E5331316C1B49@CO6PR12MB5396.namprd12.prod.outlook.com \
--to=suanmingm@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=michaelba@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@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).