From: Pascal Mazon <pascal.mazon@6wind.com>
To: ferruh.yigit@intel.com, keith.wiles@intel.com
Cc: dev@dpdk.org, Pascal Mazon <pascal.mazon@6wind.com>
Subject: [dpdk-dev] doc: detail new tap features in release note
Date: Mon, 27 Mar 2017 16:02:21 +0200 [thread overview]
Message-ID: <5c9bbc0a133787e31f860794aaf5c6d3f87e7b28.1490623267.git.pascal.mazon@6wind.com> (raw)
Signed-off-by: Pascal Mazon <pascal.mazon@6wind.com>
---
doc/guides/rel_notes/release_17_05.rst | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/doc/guides/rel_notes/release_17_05.rst b/doc/guides/rel_notes/release_17_05.rst
index dee63919efe7..4ab3e1a740c0 100644
--- a/doc/guides/rel_notes/release_17_05.rst
+++ b/doc/guides/rel_notes/release_17_05.rst
@@ -57,6 +57,17 @@ New Features
* Complete HW initialization even if SFP is not present.
* Add VF xcast promiscuous mode.
+* **Updated the tap driver.**
+
+ * Support MTU modification.
+ * Support packet type for Rx.
+ * Support segmented packets on Rx and Tx.
+ * Speed up Rx on tap when no packets are available.
+ * Support capturing traffic from another netdevice.
+ * Dynamically change link status when the underlying interface state changes.
+ * Generic flow API support for Ethernet, VLAN, IPv4, IPv6, UDP and TCP pattern
+ items with DROP, QUEUE and PASSTHRU actions for ingress traffic.
+
* **Added powerpc support for i40e and its vector PMD .**
i40e PMD and its vector PMD enabled by default in powerpc.
--
2.12.0.306.g4a9b9b3
next reply other threads:[~2017-03-27 14:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 14:02 Pascal Mazon [this message]
2017-03-27 14:52 ` Wiles, Keith
2017-03-29 11:29 ` 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=5c9bbc0a133787e31f860794aaf5c6d3f87e7b28.1490623267.git.pascal.mazon@6wind.com \
--to=pascal.mazon@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=keith.wiles@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).