DPDK patches and discussions
 help / color / mirror / Atom feed
From: Suanming Mou <suanmingm@nvidia.com>
To: <orika@nvidia.com>, Aman Singh <aman.deep.singh@intel.com>,
	Yuying Zhang <yuying.zhang@intel.com>
Cc: <rasland@nvidia.com>, <dev@dpdk.org>
Subject: [PATCH 3/3] app/testpmd: add port representor as sample destination
Date: Tue, 17 Oct 2023 08:44:01 +0800	[thread overview]
Message-ID: <20231017004401.698745-4-suanmingm@nvidia.com> (raw)
In-Reply-To: <20231017004401.698745-1-suanmingm@nvidia.com>

This commit adds the missing port representor support as sample
destination.

Signed-off-by: Suanming Mou <suanmingm@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 6c8571154e..0d521159e9 100644
--- a/app/test-pmd/cmdline_flow.c
+++ b/app/test-pmd/cmdline_flow.c
@@ -2472,6 +2472,7 @@ static const enum index next_action_sample[] = {
 	ACTION_VXLAN_ENCAP,
 	ACTION_NVGRE_ENCAP,
 	ACTION_REPRESENTED_PORT,
+	ACTION_PORT_REPRESENTOR,
 	ACTION_NEXT,
 	ZERO,
 };
-- 
2.34.1


  parent reply	other threads:[~2023-10-17  0:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17  0:43 [PATCH 0/3] net/mlx5: add port representor destination to mirror Suanming Mou
2023-10-17  0:43 ` [PATCH 1/3] net/mlx5: add port representor action Suanming Mou
2023-10-17  0:44 ` [PATCH 2/3] net/mlx5: add port representor destination to mirror Suanming Mou
2023-10-17  0:44 ` Suanming Mou [this message]
2023-10-29 13:33 ` [PATCH 0/3] " Ori Kam
2023-10-30  2:28 ` [PATCH v2 " Suanming Mou
2023-10-30  2:28   ` [PATCH v2 1/3] net/mlx5: add port representor action Suanming Mou
2023-10-30  2:28   ` [PATCH v2 2/3] net/mlx5: add port representor destination to mirror Suanming Mou
2023-10-30  2:28   ` [PATCH v2 3/3] app/testpmd: add port representor as sample destination Suanming Mou
2023-10-30  9:05   ` [PATCH v2 0/3] net/mlx5: add port representor destination to mirror 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=20231017004401.698745-4-suanmingm@nvidia.com \
    --to=suanmingm@nvidia.com \
    --cc=aman.deep.singh@intel.com \
    --cc=dev@dpdk.org \
    --cc=orika@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=yuying.zhang@intel.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).