DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dekel Peled <dekelp@nvidia.com>
To: orika@nvidia.com, thomas@monjalon.net, ferruh.yigit@intel.com,
	arybchenko@solarflare.com, wenzhuo.lu@intel.com,
	beilei.xing@intel.com, bernard.iremonger@intel.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v3 2/2] app/testpmd: support query of AGE action
Date: Wed,  7 Oct 2020 14:37:41 +0300	[thread overview]
Message-ID: <0c55291a842a9432e9f4e446d115960f438d3f04.1602070197.git.dekelp@nvidia.com> (raw)
In-Reply-To: <cover.1602070197.git.dekelp@nvidia.com>

Following ethdev update [1], this patch adds CLI support to query
information related to AGE action.

[1] https://mails.dpdk.org/archives/dev/2020-September/183699.html

Signed-off-by: Dekel Peled <dekelp@nvidia.com>
Acked-by: Matan Azrad <matan@nvidia.com>
---
 app/test-pmd/config.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/app/test-pmd/config.c b/app/test-pmd/config.c
index 418ea6d..83ef332 100644
--- a/app/test-pmd/config.c
+++ b/app/test-pmd/config.c
@@ -1770,6 +1770,7 @@ void print_valid_ports(void)
 	union {
 		struct rte_flow_query_count count;
 		struct rte_flow_action_rss rss_conf;
+		struct rte_flow_query_age age;
 	} query;
 	int ret;
 
@@ -1792,6 +1793,7 @@ void print_valid_ports(void)
 	switch (action->type) {
 	case RTE_FLOW_ACTION_TYPE_COUNT:
 	case RTE_FLOW_ACTION_TYPE_RSS:
+	case RTE_FLOW_ACTION_TYPE_AGE:
 		break;
 	default:
 		printf("Cannot query action type %d (%s)\n",
@@ -1819,6 +1821,16 @@ void print_valid_ports(void)
 	case RTE_FLOW_ACTION_TYPE_RSS:
 		rss_config_display(&query.rss_conf);
 		break;
+	case RTE_FLOW_ACTION_TYPE_AGE:
+		printf("%s:\n"
+		       " aged: %u\n"
+		       " last_hit_time_valid: %u\n"
+		       " sec_since_last_hit: %" PRIu32 "\n",
+		       name,
+		       query.age.aged,
+		       query.age.last_hit_time_valid,
+		       query.age.sec_since_last_hit);
+		break;
 	default:
 		printf("Cannot display result for action type %d (%s)\n",
 		       action->type, name);
-- 
1.8.3.1


  parent reply	other threads:[~2020-10-07 11:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30  9:04 [dpdk-dev] [PATCH] ethdev: " Dekel Peled
2020-09-30 14:50 ` Ori Kam
2020-10-01 19:32 ` [dpdk-dev] [PATCH v2 0/2] " Dekel Peled
2020-10-01 19:32   ` [dpdk-dev] [PATCH v2 1/2] ethdev: " Dekel Peled
2020-10-04 10:01     ` Ori Kam
2020-10-05 11:03       ` Dekel Peled
2020-10-01 19:32   ` [dpdk-dev] [PATCH v2 2/2] app/testpmd: " Dekel Peled
2020-10-07 11:37   ` [dpdk-dev] [PATCH v3 0/2] " Dekel Peled
2020-10-07 11:37     ` [dpdk-dev] [PATCH v3 1/2] ethdev: " Dekel Peled
2020-10-07 11:48       ` Ori Kam
2020-10-07 11:37     ` Dekel Peled [this message]
2020-10-07 13:28     ` [dpdk-dev] [PATCH v4 0/2] " Dekel Peled
2020-10-07 13:28       ` [dpdk-dev] [PATCH v4 1/2] ethdev: " Dekel Peled
2020-10-07 13:46         ` Ori Kam
2020-10-13  8:53         ` Andrew Rybchenko
2020-10-13 11:14           ` Ferruh Yigit
2020-10-07 13:28       ` [dpdk-dev] [PATCH v4 2/2] app/testpmd: " Dekel Peled

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=0c55291a842a9432e9f4e446d115960f438d3f04.1602070197.git.dekelp@nvidia.com \
    --to=dekelp@nvidia.com \
    --cc=arybchenko@solarflare.com \
    --cc=beilei.xing@intel.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=orika@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=wenzhuo.lu@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).