DPDK patches and discussions
 help / color / mirror / Atom feed
From: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
To: <dev@dpdk.org>
Cc: <matan@nvidia.com>, <rasland@nvidia.com>, <orika@nvidia.com>,
	<dsosnowski@nvidia.com>
Subject: [PATCH v2 2/6] app/testpmd: add modify IPv4 next protocol command line
Date: Wed, 7 Feb 2024 14:13:50 +0200	[thread overview]
Message-ID: <20240207121354.27175-2-viacheslavo@nvidia.com> (raw)
In-Reply-To: <20240207121354.27175-1-viacheslavo@nvidia.com>

Add new modify field action type string: "ipv4_proto".

Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Acked-by: Ori Kam <orika@nvidia.com>
Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
---
 app/test-pmd/cmdline_flow.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/app/test-pmd/cmdline_flow.c b/app/test-pmd/cmdline_flow.c
index 4062879552..03b418a5d8 100644
--- a/app/test-pmd/cmdline_flow.c
+++ b/app/test-pmd/cmdline_flow.c
@@ -962,6 +962,7 @@ static const char *const modify_field_ids[] = {
 	"geneve_opt_type", "geneve_opt_class", "geneve_opt_data", "mpls",
 	"tcp_data_off", "ipv4_ihl", "ipv4_total_len", "ipv6_payload_len",
 	"random",
+	"ipv4_proto",
 	NULL
 };
 
-- 
2.18.1


  reply	other threads:[~2024-02-07 12:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07 12:13 [PATCH v2 1/6] ethdev: add modify IPv4 next protocol field Viacheslav Ovsiienko
2024-02-07 12:13 ` Viacheslav Ovsiienko [this message]
2024-02-07 12:13 ` [PATCH v2 3/6] net/mlx5: add modify IPv4 protocol implementation Viacheslav Ovsiienko
2024-02-07 12:13 ` [PATCH v2 4/6] ethdev: add modify action support for IPsec fields Viacheslav Ovsiienko
2024-02-07 12:13 ` [PATCH v2 5/6] app/testpmd: add modify ESP related fields command line Viacheslav Ovsiienko
2024-02-07 12:13 ` [PATCH v2 6/6] net/mlx5: add modify field action IPsec support Viacheslav Ovsiienko

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=20240207121354.27175-2-viacheslavo@nvidia.com \
    --to=viacheslavo@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rasland@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).