From: Nicolas Chautru <nicolas.chautru@intel.com>
To: dev@dpdk.org, maxime.coquelin@redhat.com
Cc: hemant.agrawal@nxp.com, david.marchand@redhat.com,
hernan.vargas@intel.com,
Nicolas Chautru <nicolas.chautru@intel.com>
Subject: [PATCH v2 3/3] test/bbdev: update for queue stats
Date: Mon, 12 Aug 2024 16:42:01 -0700 [thread overview]
Message-ID: <20240812234201.2196633-4-nicolas.chautru@intel.com> (raw)
In-Reply-To: <20240812234201.2196633-1-nicolas.chautru@intel.com>
Update to include in test application the queue stats for the
enqueue_depth_avail counter.
Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
---
app/test-bbdev/test_bbdev_perf.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/app/test-bbdev/test_bbdev_perf.c b/app/test-bbdev/test_bbdev_perf.c
index 3a94f15a30..259192c670 100644
--- a/app/test-bbdev/test_bbdev_perf.c
+++ b/app/test-bbdev/test_bbdev_perf.c
@@ -5816,6 +5816,7 @@ get_bbdev_queue_stats(uint16_t dev_id, uint16_t queue_id,
stats->enqueue_warn_count = q_stats->enqueue_warn_count;
stats->dequeue_warn_count = q_stats->dequeue_warn_count;
stats->acc_offload_cycles = q_stats->acc_offload_cycles;
+ stats->enqueue_depth_avail = q_stats->enqueue_depth_avail;
return 0;
}
--
2.34.1
next prev parent reply other threads:[~2024-08-12 23:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 23:41 [PATCH v2 0/3] bbdev: sdditional " Nicolas Chautru
2024-08-12 23:41 ` [PATCH v2 1/3] bbdev: new queue stat for available enqueue depth Nicolas Chautru
2024-09-10 15:16 ` Maxime Coquelin
2024-08-12 23:42 ` [PATCH v2 2/3] baseband/acc: refactor queue status update Nicolas Chautru
2024-08-13 7:24 ` Mattia Milani
2024-08-13 7:31 ` Mattia Milani
2024-09-10 15:26 ` Maxime Coquelin
2024-08-12 23:42 ` Nicolas Chautru [this message]
2024-09-10 15:32 ` [PATCH v2 3/3] test/bbdev: update for queue stats Maxime Coquelin
2024-08-13 7:22 ` [PATCH v2 0/3] bbdev: sdditional " Hemant Agrawal
2024-09-13 13:50 ` Maxime Coquelin
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=20240812234201.2196633-4-nicolas.chautru@intel.com \
--to=nicolas.chautru@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=hernan.vargas@intel.com \
--cc=maxime.coquelin@redhat.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).