DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shiri Kuzin <shirik@nvidia.com>
To: dev@dpdk.org
Cc: viacheslavo@nvidia.com, andrew.rybchenko@oktetlabs.ru,
	olivier.matz@6wind.com, orika@nvidia.com, ferruh.yigit@intel.com,
	thomas@monjalon.net, rasland@nvidia.com
Subject: [dpdk-dev] [PATCH v2 0/6] add GTP PSC extension header support
Date: Mon, 11 Jan 2021 20:21:47 +0200	[thread overview]
Message-ID: <20210111182153.9972-1-shirik@nvidia.com> (raw)
In-Reply-To: <20201228194432.30512-1-shirik@nvidia.com>

In this patch we add the support for GTP PSC in net/mlx5.
This will enable matching on "rte_flow_item_gtp_psc" item.

The support in testpmd is extended to support raw 
encap\decap of GTP PSC.

v2:
- update documentation.
- fix PDU type shift.

Shiri Kuzin (4):
  common/mlx5: add matcher fields for GTP extensions
  net/mlx5: add GTP PSC flow validation
  net/mlx5: add GTP PSC item translation
  doc: update GTP extension header support

Viacheslav Ovsiienko (2):
  ethdev: update GTP headers
  app/testpmd: add GTP PSC option support in raw sets

 app/test-pmd/cmdline_flow.c            |  66 +++++++++-
 doc/guides/nics/mlx5.rst               |  10 ++
 doc/guides/rel_notes/release_21_02.rst |   5 +
 drivers/common/mlx5/mlx5_prm.h         |   7 +-
 drivers/net/mlx5/mlx5_flow.h           |  11 ++
 drivers/net/mlx5/mlx5_flow_dv.c        | 162 +++++++++++++++++++++++++
 lib/librte_net/rte_gtp.h               |  33 ++++-
 7 files changed, 287 insertions(+), 7 deletions(-)

-- 
2.21.0


  parent reply	other threads:[~2021-01-11 18:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-28 19:44 [dpdk-dev] [PATCH " Shiri Kuzin
2020-12-28 19:44 ` [dpdk-dev] [PATCH 1/6] ethdev: update GTP headers Shiri Kuzin
2020-12-29 10:15   ` Ori Kam
2020-12-28 19:44 ` [dpdk-dev] [PATCH 2/6] app/testpmd: add GTP PSC option support in raw sets Shiri Kuzin
2020-12-29 10:18   ` Ori Kam
2020-12-28 19:44 ` [dpdk-dev] [PATCH 3/6] common/mlx5: add matcher fields for GTP extensions Shiri Kuzin
2020-12-28 19:44 ` [dpdk-dev] [PATCH 4/6] net/mlx5: add GTP PSC flow validation Shiri Kuzin
2020-12-28 19:44 ` [dpdk-dev] [PATCH 5/6] net/mlx5: add GTP PSC item translation Shiri Kuzin
2020-12-28 19:44 ` [dpdk-dev] [PATCH 6/6] doc: update GTP extension header support Shiri Kuzin
2021-01-11 18:21 ` Shiri Kuzin [this message]
2021-01-11 18:21   ` [dpdk-dev] [PATCH v2 1/6] ethdev: update GTP headers Shiri Kuzin
2021-01-15  1:15     ` Ferruh Yigit
2021-01-11 18:21   ` [dpdk-dev] [PATCH v2 2/6] app/testpmd: add GTP PSC option support in raw sets Shiri Kuzin
2021-01-11 18:21   ` [dpdk-dev] [PATCH v2 3/6] common/mlx5: add matcher fields for GTP extensions Shiri Kuzin
2021-01-11 18:21   ` [dpdk-dev] [PATCH v2 4/6] net/mlx5: add GTP PSC flow validation Shiri Kuzin
2021-01-11 18:21   ` [dpdk-dev] [PATCH v2 5/6] net/mlx5: add GTP PSC item translation Shiri Kuzin
2021-01-11 18:21   ` [dpdk-dev] [PATCH v2 6/6] doc: update GTP extension header support Shiri Kuzin
2021-01-15  1:16   ` [dpdk-dev] [PATCH v2 0/6] add GTP PSC " Ferruh Yigit

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=20210111182153.9972-1-shirik@nvidia.com \
    --to=shirik@nvidia.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=olivier.matz@6wind.com \
    --cc=orika@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=thomas@monjalon.net \
    --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).