From: Chenxu Di <chenxux.di@intel.com>
To: dev@dpdk.org
Cc: Yang Qiming <qiming.yang@intel.com>,
beilei.xing@intel.com, Chenxu Di <chenxux.di@intel.com>
Subject: [dpdk-dev] [PATCH v5 4/4] net/e1000: cleanup Tx buffers
Date: Fri, 27 Dec 2019 03:45:20 +0000 [thread overview]
Message-ID: <20191227034520.78613-5-chenxux.di@intel.com> (raw)
In-Reply-To: <20191227034520.78613-1-chenxux.di@intel.com>
Add support to the igb vf for the API rte_eth_tx_done_cleanup
to force free consumed buffers on Tx ring.
Signed-off-by: Chenxu Di <chenxux.di@intel.com>
---
drivers/net/e1000/igb_ethdev.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/e1000/igb_ethdev.c b/drivers/net/e1000/igb_ethdev.c
index a3e30dbe5..647d5504f 100644
--- a/drivers/net/e1000/igb_ethdev.c
+++ b/drivers/net/e1000/igb_ethdev.c
@@ -446,6 +446,7 @@ static const struct eth_dev_ops igbvf_eth_dev_ops = {
.tx_descriptor_status = eth_igb_tx_descriptor_status,
.tx_queue_setup = eth_igb_tx_queue_setup,
.tx_queue_release = eth_igb_tx_queue_release,
+ .tx_done_cleanup = eth_igb_tx_done_cleanup,
.set_mc_addr_list = eth_igb_set_mc_addr_list,
.rxq_info_get = igb_rxq_info_get,
.txq_info_get = igb_txq_info_get,
--
2.17.1
next prev parent reply other threads:[~2019-12-27 4:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <“20191203055134.72874-1-chenxux.di@intel.comâ€>
2019-12-27 3:45 ` [dpdk-dev] [PATCH v5 0/4] drivers/net: " Chenxu Di
2019-12-27 3:45 ` [dpdk-dev] [PATCH v5 1/4] net/i40e: " Chenxu Di
2019-12-30 3:17 ` Yang, Qiming
2019-12-27 3:45 ` [dpdk-dev] [PATCH v5 2/4] net/ice: " Chenxu Di
2019-12-30 3:29 ` Yang, Qiming
2019-12-27 3:45 ` [dpdk-dev] [PATCH v5 3/4] net/ixgbe: " Chenxu Di
2019-12-30 3:29 ` Yang, Qiming
2019-12-27 3:45 ` Chenxu Di [this message]
2019-12-27 8:25 ` [dpdk-dev] [PATCH v5 0/4] drivers/net: " Zhang, Xiao
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=20191227034520.78613-5-chenxux.di@intel.com \
--to=chenxux.di@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=qiming.yang@intel.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).