From: Haiyue Wang <haiyue.wang@intel.com>
To: dev@dpdk.org, ferruh.yigit@intel.com, mdr@ashroe.eu,
chenmin.sun@intel.com
Cc: Haiyue Wang <haiyue.wang@intel.com>
Subject: [dpdk-dev] [RFC v3 4/4] app/testpmd: show the Rx/Tx burst mode description
Date: Wed, 11 Sep 2019 00:33:37 +0800 [thread overview]
Message-ID: <20190910163337.4843-5-haiyue.wang@intel.com> (raw)
In-Reply-To: <20190910163337.4843-1-haiyue.wang@intel.com>
Add the 'Burst mode' section into command 'show rxq|txq info <port_id>
<queue_id>' to show the Rx/Tx burst mode description like:
"Burst mode: Vector AVX2 Scattered"
Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
---
app/test-pmd/config.c | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
diff --git a/app/test-pmd/config.c b/app/test-pmd/config.c
index 1a5a5c13c..d10ad6cfa 100644
--- a/app/test-pmd/config.c
+++ b/app/test-pmd/config.c
@@ -324,9 +324,21 @@ nic_stats_mapping_display(portid_t port_id)
nic_stats_mapping_border, nic_stats_mapping_border);
}
+static void
+burst_mode_options_display(uint64_t options)
+{
+ uint64_t opt;
+
+ for (opt = 1; options != 0; opt <<= 1, options >>= 1) {
+ if (options & 1)
+ printf(" %s", rte_eth_burst_mode_option_name(opt));
+ }
+}
+
void
rx_queue_infos_display(portid_t port_id, uint16_t queue_id)
{
+ struct rte_eth_burst_mode mode;
struct rte_eth_rxq_info qinfo;
int32_t rc;
static const char *info_border = "*********************";
@@ -354,12 +366,19 @@ rx_queue_infos_display(portid_t port_id, uint16_t queue_id)
printf("\nRX scattered packets: %s",
(qinfo.scattered_rx != 0) ? "on" : "off");
printf("\nNumber of RXDs: %hu", qinfo.nb_desc);
+
+ if (rte_eth_rx_burst_mode_get(port_id, queue_id, &mode) == 0) {
+ printf("\nBurst mode:");
+ burst_mode_options_display(mode.options);
+ }
+
printf("\n");
}
void
tx_queue_infos_display(portid_t port_id, uint16_t queue_id)
{
+ struct rte_eth_burst_mode mode;
struct rte_eth_txq_info qinfo;
int32_t rc;
static const char *info_border = "*********************";
@@ -383,6 +402,12 @@ tx_queue_infos_display(portid_t port_id, uint16_t queue_id)
printf("\nTX deferred start: %s",
(qinfo.conf.tx_deferred_start != 0) ? "on" : "off");
printf("\nNumber of TXDs: %hu", qinfo.nb_desc);
+
+ if (rte_eth_tx_burst_mode_get(port_id, queue_id, &mode) == 0) {
+ printf("\nBurst mode:");
+ burst_mode_options_display(mode.options);
+ }
+
printf("\n");
}
--
2.17.1
next prev parent reply other threads:[~2019-09-10 16:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 16:33 [dpdk-dev] [RFC v3 0/4] get Rx/Tx packet burst mode information Haiyue Wang
2019-09-10 16:33 ` [dpdk-dev] [RFC v3 1/4] ethdev: add the API for getting " Haiyue Wang
2019-09-10 16:33 ` [dpdk-dev] [RFC v3 2/4] net/i40e: support to get the Rx/Tx burst mode Haiyue Wang
2019-09-10 16:33 ` [dpdk-dev] [RFC v3 3/4] net/ice: " Haiyue Wang
2019-09-10 16:33 ` Haiyue Wang [this message]
2019-09-12 16:07 ` [dpdk-dev] [RFC v3 4/4] app/testpmd: show the Rx/Tx burst mode description Iremonger, Bernard
2019-09-25 16:33 ` Wang, Haiyue
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=20190910163337.4843-5-haiyue.wang@intel.com \
--to=haiyue.wang@intel.com \
--cc=chenmin.sun@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=mdr@ashroe.eu \
/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).