From: Haiyue Wang <haiyue.wang@intel.com>
To: dev@dpdk.org
Cc: Haiyue Wang <haiyue.wang@intel.com>
Subject: [dpdk-dev] [RFC v1 1/3] ethdev: add the Rx/Tx burst description field in queue information
Date: Mon, 12 Aug 2019 22:15:03 +0800 [thread overview]
Message-ID: <1565619305-17116-2-git-send-email-haiyue.wang@intel.com> (raw)
In-Reply-To: <1565619305-17116-1-git-send-email-haiyue.wang@intel.com>
Since each PMD has different Rx/Tx burst capabilities such as Vector,
Scattered, Bulk etc, adding the Rx/Tx burst description field in queue
information to provide apps current configuration of PMD Rx/Tx burst.
This is a self-description for each PMD in its own format.
Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
---
lib/librte_ethdev/rte_ethdev.h | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/lib/librte_ethdev/rte_ethdev.h b/lib/librte_ethdev/rte_ethdev.h
index dc6596b..bc48c0c 100644
--- a/lib/librte_ethdev/rte_ethdev.h
+++ b/lib/librte_ethdev/rte_ethdev.h
@@ -1192,6 +1192,9 @@ struct rte_eth_dev_info {
struct rte_eth_switch_info switch_info;
};
+/** Maximum information length to describe the PMD RX/TX functions */
+#define RTE_PMD_BURST_INFO_SIZE 128
+
/**
* Ethernet device RX queue information structure.
* Used to retrieve information about configured queue.
@@ -1201,6 +1204,8 @@ struct rte_eth_rxq_info {
struct rte_eth_rxconf conf; /**< queue config parameters. */
uint8_t scattered_rx; /**< scattered packets RX supported. */
uint16_t nb_desc; /**< configured number of RXDs. */
+ char burst_info[RTE_PMD_BURST_INFO_SIZE];
+ /**< Description of PMD RX function, such as Vector, Scattered etc */
} __rte_cache_min_aligned;
/**
@@ -1210,6 +1215,8 @@ struct rte_eth_rxq_info {
struct rte_eth_txq_info {
struct rte_eth_txconf conf; /**< queue config parameters. */
uint16_t nb_desc; /**< configured number of TXDs. */
+ char burst_info[RTE_PMD_BURST_INFO_SIZE];
+ /**< Description of PMD TX function, such as Vector, Scattered etc */
} __rte_cache_min_aligned;
/** Maximum name length for extended statistics counters */
--
2.7.4
next prev parent 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 [dpdk-dev] [RFC v1 0/3] show the Rx/Tx burst description field Haiyue Wang
2019-08-12 14:15 ` Haiyue Wang [this message]
2019-08-12 15:37 ` [dpdk-dev] [RFC v1 1/3] ethdev: add the Rx/Tx burst description field in queue information 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-2-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).