DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shrikrishna Khare <skhare@vmware.com>
To: <yongwang@vmware.com>
Cc: <dev@dpdk.org>, Shrikrishna Khare <skhare@vmware.com>
Subject: [dpdk-dev]  [PATCH v3 7/7] net/vmxnet3: update to version 3
Date: Mon, 6 Mar 2017 14:55:07 -0800	[thread overview]
Message-ID: <1488840907-17441-8-git-send-email-skhare@vmware.com> (raw)
In-Reply-To: <1488840907-17441-1-git-send-email-skhare@vmware.com>

With all vmxnet3 version 3 changes incorporated in the vmxnet3 driver,
the driver can configure emulation to run at vmxnet3 version 3, provided
the emulation advertises support for version 3.

This patch also updates release notes.

Signed-off-by: Shrikrishna Khare <skhare@vmware.com>
Acked-by: Yong Wang <yongwang@vmware.com>
Acked-by: Jin Heo <heoj@vmware.com>
---
 doc/guides/rel_notes/release_17_05.rst | 6 ++++++
 drivers/net/vmxnet3/vmxnet3_ethdev.c   | 6 +++++-
 2 files changed, 11 insertions(+), 1 deletion(-)

diff --git a/doc/guides/rel_notes/release_17_05.rst b/doc/guides/rel_notes/release_17_05.rst
index e25ea9f..cbe6233 100644
--- a/doc/guides/rel_notes/release_17_05.rst
+++ b/doc/guides/rel_notes/release_17_05.rst
@@ -41,6 +41,12 @@ New Features
      Also, make sure to start the actual text at the margin.
      =========================================================
 
+   * **Added vmxnet3 version 3 support.**
+
+     Added support for vmxnet3 version 3 which includes several
+     performance enhancements viz. configurable TX data ring, Receive
+     Data Ring, ability to register memory regions.
+
 
 Resolved Issues
 ---------------
diff --git a/drivers/net/vmxnet3/vmxnet3_ethdev.c b/drivers/net/vmxnet3/vmxnet3_ethdev.c
index 96f1585..01da7e3 100644
--- a/drivers/net/vmxnet3/vmxnet3_ethdev.c
+++ b/drivers/net/vmxnet3/vmxnet3_ethdev.c
@@ -284,7 +284,11 @@ eth_vmxnet3_dev_init(struct rte_eth_dev *eth_dev)
 	ver = VMXNET3_READ_BAR1_REG(hw, VMXNET3_REG_VRRS);
 	PMD_INIT_LOG(DEBUG, "Hardware version : %d", ver);
 
-	if (ver & (1 << VMXNET3_REV_2)) {
+	if (ver & (1 << VMXNET3_REV_3)) {
+		VMXNET3_WRITE_BAR1_REG(hw, VMXNET3_REG_VRRS,
+				       1 << VMXNET3_REV_3);
+		hw->version = VMXNET3_REV_3 + 1;
+	} else if (ver & (1 << VMXNET3_REV_2)) {
 		VMXNET3_WRITE_BAR1_REG(hw, VMXNET3_REG_VRRS,
 				       1 << VMXNET3_REV_2);
 		hw->version = VMXNET3_REV_2 + 1;
-- 
2.6.2

  parent reply	other threads:[~2017-03-06 22:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06 22:55 [dpdk-dev] [PATCH v3 0/7] vmxnet3: upgrade " Shrikrishna Khare
2017-03-06 22:55 ` [dpdk-dev] [PATCH v3 1/7] net/vmxnet3: prepare for version 3 changes Shrikrishna Khare
2017-03-06 22:55 ` [dpdk-dev] [PATCH v3 2/7] net/vmxnet3: introduce generalized cmd interface Shrikrishna Khare
2017-03-06 22:55 ` [dpdk-dev] [PATCH v3 3/7] net/vmxnet3: variable length transmit data ring Shrikrishna Khare
2017-03-06 22:55 ` [dpdk-dev] [PATCH v3 4/7] net/vmxnet3: add receive data ring support Shrikrishna Khare
2017-03-06 22:55 ` [dpdk-dev] [PATCH v3 5/7] net/vmxnet3: add reserved version 3 command Shrikrishna Khare
2017-03-06 22:55 ` [dpdk-dev] [PATCH v3 6/7] net/vmxnet3: add cmd to register memory region Shrikrishna Khare
2017-03-06 22:55 ` Shrikrishna Khare [this message]
2017-03-07 12:21 ` [dpdk-dev] [PATCH v3 0/7] vmxnet3: upgrade to version 3 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=1488840907-17441-8-git-send-email-skhare@vmware.com \
    --to=skhare@vmware.com \
    --cc=dev@dpdk.org \
    --cc=yongwang@vmware.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).