DPDK patches and discussions
 help / color / mirror / Atom feed
From: Wei Zhao <wei.zhao1@intel.com>
To: dev@dpdk.org
Cc: wenzhuo.lu@intel.com, qi.z.zhang@intel.com,
	Wei Zhao <wei.zhao1@intel.com>
Subject: [dpdk-dev] [PATCH v2] net/e1000: add support for check descriptor status APIs
Date: Wed, 20 Jun 2018 16:52:53 +0800	[thread overview]
Message-ID: <1529484773-6008-1-git-send-email-wei.zhao1@intel.com> (raw)
In-Reply-To: <20180208083630.103388-2-wei.zhao1@intel.com>

Igb VF nic need to support check descriptor status APIs, they are
rte_eth_rx_descriptor_status and rte_eth_tx_descriptor_status.
So, this patch add ops with function pointer that enable feature.

Signed-off-by: Wei Zhao <wei.zhao1@intel.com>

---

v2:
add release note document info.
---
 doc/guides/rel_notes/release_18_08.rst | 4 ++--
 drivers/net/e1000/igb_ethdev.c         | 3 +++
 2 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/doc/guides/rel_notes/release_18_08.rst b/doc/guides/rel_notes/release_18_08.rst
index 5baa09e..f9bb135 100644
--- a/doc/guides/rel_notes/release_18_08.rst
+++ b/doc/guides/rel_notes/release_18_08.rst
@@ -41,9 +41,9 @@ New Features
      Also, make sure to start the actual text at the margin.
      =========================================================
 
-* **Added fm10k ethernet driver to support check descriptor status APIs.**
+* **Added fm10k and igb VF ethernet driver to support check descriptor status APIs.**
 
-    Fm10k nic need to support check descriptor status APIs, they are
+    Fm10k and igb VF nic need to support check descriptor status APIs, they are
     rte_eth_rx_descriptor_status and rte_eth_tx_descriptor_status.
     add ops pointer with new function which enable feature.
 
diff --git a/drivers/net/e1000/igb_ethdev.c b/drivers/net/e1000/igb_ethdev.c
index edc7be3..f5b02b2 100644
--- a/drivers/net/e1000/igb_ethdev.c
+++ b/drivers/net/e1000/igb_ethdev.c
@@ -435,6 +435,9 @@ static const struct eth_dev_ops igbvf_eth_dev_ops = {
 	.dev_supported_ptypes_get = eth_igb_supported_ptypes_get,
 	.rx_queue_setup       = eth_igb_rx_queue_setup,
 	.rx_queue_release     = eth_igb_rx_queue_release,
+	.rx_descriptor_done   = eth_igb_rx_descriptor_done,
+	.rx_descriptor_status = eth_igb_rx_descriptor_status,
+	.tx_descriptor_status = eth_igb_tx_descriptor_status,
 	.tx_queue_setup       = eth_igb_tx_queue_setup,
 	.tx_queue_release     = eth_igb_tx_queue_release,
 	.set_mc_addr_list     = eth_igb_set_mc_addr_list,
-- 
2.7.5

  reply	other threads:[~2018-06-20  9:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-08  8:36 [dpdk-dev] [PATCH 0/2] " Wei Zhao
2018-02-08  8:36 ` [dpdk-dev] [PATCH 1/2] net/e1000: " Wei Zhao
2018-06-20  8:52   ` Wei Zhao [this message]
2018-06-27  8:37     ` [dpdk-dev] [PATCH v3] " Wei Zhao
2018-06-29  1:52       ` [dpdk-dev] [PATCH v4] " Wei Zhao
2018-07-02  7:42         ` Zhao1, Wei
2018-07-02 13:03           ` Zhang, Qi Z
2018-07-02 13:12             ` Zhang, Qi Z
2018-02-08  8:36 ` [dpdk-dev] [PATCH 2/2] net/fm10k: " Wei Zhao
2018-06-20  8:44   ` [dpdk-dev] [PATCH v2] " Wei Zhao
2018-06-22  7:53     ` [dpdk-dev] [PATCH v3] " Wei Zhao
2018-06-22  8:20       ` [dpdk-dev] [PATCH v4] " Wei Zhao
2018-06-27  8:10         ` Zhang, Qi Z
2018-06-27  8:18           ` Zhao1, Wei
2018-06-27  8:18         ` Zhang, Qi Z
2018-06-27  9:09           ` Zhao1, Wei
2018-06-27  8:24         ` [dpdk-dev] [PATCH v5] " Wei Zhao
2018-06-27  8:26         ` Wei Zhao
2018-06-29  1:48           ` [dpdk-dev] [PATCH v6] " Wei Zhao
2018-06-29 11:03             ` Ferruh Yigit
2018-07-02  1:46               ` Zhao1, Wei
2018-07-02  7:15             ` [dpdk-dev] [PATCH v7] " Zhao Wei
2018-07-02 13:07               ` Zhang, Qi Z
2018-07-02 13:11                 ` Zhang, Qi Z
2018-06-27 12:49         ` [dpdk-dev] [PATCH v4] " Zhang, Qi Z
2018-06-29  1:22           ` Zhao1, Wei

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=1529484773-6008-1-git-send-email-wei.zhao1@intel.com \
    --to=wei.zhao1@intel.com \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@intel.com \
    --cc=wenzhuo.lu@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).