DPDK patches and discussions
 help / color / mirror / Atom feed
From: Michael Baum <michaelba@nvidia.com>
To: <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>,
	Raslan Darawsheh <rasland@nvidia.com>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Subject: [PATCH v3 0/2] net/mlx5: support MPLSoUDP for HWS
Date: Thu, 23 Feb 2023 09:47:32 +0200	[thread overview]
Message-ID: <20230223074734.3315320-1-michaelba@nvidia.com> (raw)
In-Reply-To: <20230222212310.3295762-1-michaelba@nvidia.com>

Add support for matching/encap/decap MPLSoUDP including multiple MPLS
headers.

v2:
 - Rebase.
 - Fix typo in comment.

v3:
 - Update to capital letters at the beginning of sentences in comments.

Erez Shitrit (1):
  net/mlx5/hws: support matching on MPLSoUDP

Michael Baum (1):
  net/mlx5: add MPLS tunnel support for HWS

 doc/guides/nics/mlx5.rst               |   4 +
 doc/guides/rel_notes/release_23_03.rst |   1 +
 drivers/net/mlx5/hws/mlx5dr_definer.c  | 183 ++++++++++++++++++++++++-
 drivers/net/mlx5/hws/mlx5dr_definer.h  |  32 ++++-
 drivers/net/mlx5/mlx5_flow_hw.c        |   1 +
 5 files changed, 218 insertions(+), 3 deletions(-)

-- 
2.25.1


  parent reply	other threads:[~2023-02-23  7:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 21:23 [PATCH v2 " 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 ` Michael Baum [this message]
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
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=20230223074734.3315320-1-michaelba@nvidia.com \
    --to=michaelba@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@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).