From: John Daley <johndale@cisco.com>
To: john.mcnamara@intel.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] doc: update release notes with enic PMD changes
Date: Thu, 3 Nov 2016 11:01:33 -0700 [thread overview]
Message-ID: <20161103180133.20000-1-johndale@cisco.com> (raw)
Signed-off-by: John Daley <johndale@cisco.com>
---
doc/guides/nics/features/enic.ini | 2 +-
doc/guides/rel_notes/release_16_11.rst | 14 ++++++++++++++
2 files changed, 15 insertions(+), 1 deletion(-)
diff --git a/doc/guides/nics/features/enic.ini b/doc/guides/nics/features/enic.ini
index 523d4f1..86576a7 100644
--- a/doc/guides/nics/features/enic.ini
+++ b/doc/guides/nics/features/enic.ini
@@ -7,7 +7,7 @@
Link status = Y
Link status event = Y
Queue start/stop = Y
-MTU update = P
+MTU update = Y
Jumbo frame = Y
Scattered Rx = Y
Promiscuous mode = Y
diff --git a/doc/guides/rel_notes/release_16_11.rst b/doc/guides/rel_notes/release_16_11.rst
index 26cdd62..4427c52 100644
--- a/doc/guides/rel_notes/release_16_11.rst
+++ b/doc/guides/rel_notes/release_16_11.rst
@@ -131,6 +131,15 @@ New Features
The GCC 4.9 ``-march`` option supports the Intel processor code names.
The config option ``RTE_MACHINE`` can be used to pass code names to the compiler as ``-march`` flag.
+* **Updated the enic driver.**
+
+ The following changes were made to enic:
+
+ * Use interrupt for link status checking instead of polling
+ * More flow director modes on UCS Blade with firmware version >= 2.0(13e)
+ * Full support for MTU update
+ * Support for rte_eth_rx_queue_count function
+ * Several bug fixes
Resolved Issues
---------------
@@ -153,6 +162,11 @@ EAL
Drivers
~~~~~~~
+* **enic: Fixed several flow director issues **
+
+* **enic: Fixed inadvertent setting of L4 checksum ptype on ICMP packets
+
+* **enic: Fixed high driver overhead when servicing Rx queues beyond the first
Libraries
~~~~~~~~~
--
2.10.0
next reply other threads:[~2016-11-03 18:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 18:01 John Daley [this message]
2016-11-04 9:29 ` Mcnamara, John
2016-11-07 17:11 ` Thomas Monjalon
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=20161103180133.20000-1-johndale@cisco.com \
--to=johndale@cisco.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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).