From: Haiyue Wang <haiyue.wang@intel.com>
To: dev@dpdk.org
Cc: Haiyue Wang <haiyue.wang@intel.com>
Subject: [dpdk-dev] [RFC v1 0/3] show the Rx/Tx burst description field
Date: Mon, 12 Aug 2019 22:15:02 +0800 [thread overview]
Message-ID: <1565619305-17116-1-git-send-email-haiyue.wang@intel.com> (raw)
Since some PMDs have multi-path for Rx/Tx, FD.io VPP will tell you in
the Debug CLI what rx/tx function is being used:
#show hardware-interface
tx burst function: ice_xmit_pkts
rx burst function: ice_recv_scattered_pkts
But if the tx/rx is static, then 'dladdr' will return nil:
tx burst function: (nil) │······················
rx burst function: (nil) │······················
For making things consistent and gracefull, we introduce an new string
field to describe the Rx/Tx burst information. This is vendor-neutral,
it is used to identify the Rx/Tx burst selection if the PMD has more
than one.
If a PMD supports this, then rxqinfo/txqinfo->burst_info[0] != '\0'.
This is for net/ice PMD result.
testpmd> show rxq info 0 0
********************* Infos for port 0 , RX queue 0 *********************
Mempool: mbuf_pool_socket_0
RX prefetch threshold: 0
RX host threshold: 0
RX writeback threshold: 0
RX free threshold: 32
RX drop packets: off
RX deferred start: off
RX scattered packets: on
Number of RXDs: 1024
Burst description: AVX2 Vector Scattered Rx <------------ NEW
testpmd> show txq info 0 0
********************* Infos for port 0 , TX queue 0 *********************
TX prefetch threshold: 32
TX host threshold: 0
TX writeback threshold: 0
TX RS threshold: 32
TX free threshold: 32
TX deferred start: off
Number of TXDs: 1024
Burst description: AVX2 Vector Tx <------------ NEW
Haiyue Wang (3):
ethdev: add the Rx/Tx burst description field in queue information
testpmd: show the Rx/Tx burst description field in queue
net/ice: support the Rx/Tx burst description field in queue
information
app/test-pmd/config.c | 2 ++
drivers/net/ice/ice_rxtx.c | 49 ++++++++++++++++++++++++++++++++++++++++++
lib/librte_ethdev/rte_ethdev.h | 7 ++++++
3 files changed, 58 insertions(+)
--
2.7.4
next reply other threads:[~2019-08-12 14:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 14:15 Haiyue Wang [this message]
2019-08-12 14:15 ` [dpdk-dev] [RFC v1 1/3] ethdev: add the Rx/Tx burst description field in queue information Haiyue Wang
2019-08-12 15:37 ` Stephen Hemminger
2019-08-12 14:15 ` [dpdk-dev] [RFC v1 2/3] testpmd: show the Rx/Tx burst description field in queue Haiyue Wang
2019-08-12 14:15 ` [dpdk-dev] [RFC v1 3/3] net/ice: support the Rx/Tx burst description field in queue information Haiyue Wang
2019-08-12 14:27 ` [dpdk-dev] [RFC v1 0/3] show the Rx/Tx burst description field David Marchand
2019-08-12 15:38 ` Stephen Hemminger
2019-08-12 15:42 ` Wang, Haiyue
2019-08-12 15:54 ` Stephen Hemminger
2019-08-12 16:00 ` Wang, Haiyue
2019-08-12 17:28 ` Stephen Hemminger
2019-08-12 17:36 ` Wang, Haiyue
2019-08-12 15:39 ` 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=1565619305-17116-1-git-send-email-haiyue.wang@intel.com \
--to=haiyue.wang@intel.com \
--cc=dev@dpdk.org \
/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).