From: Haiyue Wang <haiyue.wang@intel.com>
To: dev@dpdk.org
Cc: mdr@ashroe.eu, thomas@monjalon.net,
Haiyue Wang <haiyue.wang@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: [dpdk-dev] [PATCH v1 3/3] ethdev: promote burst mode API to stable
Date: Wed, 1 Sep 2021 13:07:07 +0800 [thread overview]
Message-ID: <20210901050707.570163-4-haiyue.wang@intel.com> (raw)
In-Reply-To: <20210901050707.570163-1-haiyue.wang@intel.com>
The DPDK Symbol Bot reports:
Please note the symbols listed below have expired. In line with the
DPDK ABI policy, they should be scheduled for removal, in the next
DPDK release.
Symbol
rte_eth_rx_burst_mode_get
rte_eth_tx_burst_mode_get
Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
---
lib/ethdev/rte_ethdev.h | 2 --
lib/ethdev/version.map | 4 ++--
2 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/lib/ethdev/rte_ethdev.h b/lib/ethdev/rte_ethdev.h
index d2b27c351f..3277e8f8fb 100644
--- a/lib/ethdev/rte_ethdev.h
+++ b/lib/ethdev/rte_ethdev.h
@@ -4361,7 +4361,6 @@ int rte_eth_tx_queue_info_get(uint16_t port_id, uint16_t queue_id,
* - -ENOTSUP: routine is not supported by the device PMD.
* - -EINVAL: The queue_id is out of range.
*/
-__rte_experimental
int rte_eth_rx_burst_mode_get(uint16_t port_id, uint16_t queue_id,
struct rte_eth_burst_mode *mode);
@@ -4383,7 +4382,6 @@ int rte_eth_rx_burst_mode_get(uint16_t port_id, uint16_t queue_id,
* - -ENOTSUP: routine is not supported by the device PMD.
* - -EINVAL: The queue_id is out of range.
*/
-__rte_experimental
int rte_eth_tx_burst_mode_get(uint16_t port_id, uint16_t queue_id,
struct rte_eth_burst_mode *mode);
diff --git a/lib/ethdev/version.map b/lib/ethdev/version.map
index 3eece75b72..6a12b0664a 100644
--- a/lib/ethdev/version.map
+++ b/lib/ethdev/version.map
@@ -87,6 +87,7 @@ DPDK_22 {
rte_eth_promiscuous_get;
rte_eth_remove_rx_callback;
rte_eth_remove_tx_callback;
+ rte_eth_rx_burst_mode_get;
rte_eth_rx_queue_info_get;
rte_eth_rx_queue_setup;
rte_eth_set_queue_rate_limit;
@@ -104,6 +105,7 @@ DPDK_22 {
rte_eth_tx_buffer_drop_callback;
rte_eth_tx_buffer_init;
rte_eth_tx_buffer_set_err_callback;
+ rte_eth_tx_burst_mode_get;
rte_eth_tx_done_cleanup;
rte_eth_tx_queue_info_get;
rte_eth_tx_queue_setup;
@@ -166,9 +168,7 @@ EXPERIMENTAL {
# added in 19.11
rte_eth_dev_hairpin_capability_get;
- rte_eth_rx_burst_mode_get;
rte_eth_rx_hairpin_queue_setup;
- rte_eth_tx_burst_mode_get;
rte_eth_tx_hairpin_queue_setup;
rte_flow_dynf_metadata_offs;
rte_flow_dynf_metadata_mask;
--
2.33.0
next prev parent reply other threads:[~2021-09-01 5:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 5:07 [dpdk-dev] [PATCH v1 0/3] Promote some " Haiyue Wang
2021-09-01 5:07 ` [dpdk-dev] [PATCH v1 1/3] net/ixgbe: promote " Haiyue Wang
2021-09-01 9:02 ` Ferruh Yigit
2021-09-01 11:13 ` Wang, Haiyue
2021-09-01 13:55 ` Kinsella, Ray
2021-09-01 5:07 ` [dpdk-dev] [PATCH v1 2/3] net/ice: " Haiyue Wang
2021-09-01 5:07 ` Haiyue Wang [this message]
2021-09-01 9:07 ` [dpdk-dev] [PATCH v1 3/3] ethdev: promote burst mode " Ferruh Yigit
2021-09-01 13:49 ` Kinsella, Ray
2021-09-06 5:56 ` [dpdk-dev] [PATCH v2] " Haiyue Wang
2021-09-06 6:36 ` Andrew Rybchenko
2021-09-15 8:46 ` Ferruh Yigit
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=20210901050707.570163-4-haiyue.wang@intel.com \
--to=haiyue.wang@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=mdr@ashroe.eu \
--cc=thomas@monjalon.net \
/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).