DPDK patches and discussions
 help / color / mirror / Atom feed
From: Gerry Gribbon <ggribbon@nvidia.com>
To: <dev@dpdk.org>
Cc: <jamhunter@nvidia.com>, <ggribbon@nvidia.com>,
	Ori Kam <orika@nvidia.com>
Subject: [PATCH] regexdev: display response flags value
Date: Thu, 1 Sep 2022 08:29:17 +0000	[thread overview]
Message-ID: <20220901082917.2435000-1-ggribbon@nvidia.com> (raw)

Allows application user to see response flags

Signed-off-by: Gerry Gribbon <ggribbon@nvidia.com>
Acked-by: Ori Kam <orika@nvidia.com>
---
 app/test-regex/main.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/app/test-regex/main.c b/app/test-regex/main.c
index 351c36a879..94b767e380 100644
--- a/app/test-regex/main.c
+++ b/app/test-regex/main.c
@@ -392,6 +392,7 @@ run_regex(void *args)
 	uint16_t qp_id;
 	uint16_t dev_id = 0;
 	uint8_t nb_matches;
+	uint16_t rsp_flags = 0;
 	struct rte_regexdev_match *match;
 	long pos;
 	unsigned long d_ind = 0;
@@ -585,8 +586,9 @@ run_regex(void *args)
 		/* Log results per job. */
 		for (d_ind = 0; d_ind < qp->total_dequeue; d_ind++) {
 			nb_matches = qp->ops[d_ind % actual_jobs]->nb_matches;
-			printf("Job id %"PRIu64" number of matches = %d\n",
-					qp->ops[d_ind]->user_id, nb_matches);
+			rsp_flags = qp->ops[d_ind % actual_jobs]->rsp_flags;
+			printf("Job id %"PRIu64" number of matches = %d, rsp flags = 0x%x\n",
+					qp->ops[d_ind]->user_id, nb_matches, rsp_flags);
 			qp->total_matches += nb_matches;
 			match = qp->ops[d_ind % actual_jobs]->matches;
 			for (i = 0; i < nb_matches; i++) {
-- 
2.25.1


             reply	other threads:[~2022-09-01  8:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01  8:29 Gerry Gribbon [this message]
2022-10-09 13:01 ` Thomas Monjalon

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=20220901082917.2435000-1-ggribbon@nvidia.com \
    --to=ggribbon@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=jamhunter@nvidia.com \
    --cc=orika@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).