DPDK patches and discussions
 help / color / mirror / Atom feed
From: Rongwei Liu <rongweil@nvidia.com>
To: <dev@dpdk.org>, <matan@nvidia.com>, <viacheslavo@nvidia.com>,
	<orika@nvidia.com>, <thomas@monjalon.net>
Subject: [RFC v1 0/2] add IPv6 extenstion push remove
Date: Mon, 17 Apr 2023 05:26:28 +0300	[thread overview]
Message-ID: <20230417022630.2377505-1-rongweil@nvidia.com> (raw)

Add new rte actions to support push/remove IPv6 extension header.

Rongwei Liu (2):
  ethdev: add IPv6 extension push remove action
  app/testpmd: add IPv6 extension push remove cli

 app/test-pmd/cmdline_flow.c        | 443 ++++++++++++++++++++++++++++-
 doc/guides/prog_guide/rte_flow.rst |  21 ++
 lib/ethdev/rte_flow.c              |   2 +
 lib/ethdev/rte_flow.h              |  52 ++++
 4 files changed, 517 insertions(+), 1 deletion(-)

-- 
2.27.0


             reply	other threads:[~2023-04-17  2:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17  2:26 Rongwei Liu [this message]
2023-04-17  2:26 ` [RFC v1 1/2] ethdev: add IPv6 extension push remove action Rongwei Liu
2023-04-17  2:26 ` [RFC v1 2/2] app/testpmd: add IPv6 extension push remove cli Rongwei Liu

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=20230417022630.2377505-1-rongweil@nvidia.com \
    --to=rongweil@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=orika@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).