From: Shahaf Shuler <shahafs@mellanox.com>
To: john.mcnamara@intel.com
Cc: dev@dpdk.org, olgas@mellanox.com
Subject: [dpdk-dev] [PATCH] doc: update mlx4 and mlx5 release notes
Date: Tue, 25 Apr 2017 14:49:58 +0300 [thread overview]
Message-ID: <20170425114958.151811-1-shahafs@mellanox.com> (raw)
Update release notes for 17.05.
Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
---
doc/guides/rel_notes/release_17_05.rst | 18 ++++++++++++------
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/doc/guides/rel_notes/release_17_05.rst b/doc/guides/rel_notes/release_17_05.rst
index ad20e8608..7d1c77983 100644
--- a/doc/guides/rel_notes/release_17_05.rst
+++ b/doc/guides/rel_notes/release_17_05.rst
@@ -136,15 +136,21 @@ New Features
* QinQ is not supported in Vector Mode on the i40e PMD.
* Vector Mode must be disabled when using the QinQ Cloud Filter.
-* **Added TSO support for tunneled and non-tunneled packets on mlx5 driver.**
+* **Update mlx5 PMD.**
- Added support for Hardware TSO for tunneled and non-tunneled packets.
- Tunneling protocols supported are GRE and VXLAN.
+ * Support ether type in flow item.
+ * Extend IPv6 flow item with Vtc flow, Protocol and Hop limit.
+ * Support flag flow action.
+ * Support RSS action flow rule.
+ * Support TSO for tunneled and non-tunneled packets.
+ * Support Hardware checksum offloads for tunneled packets.
+ * Support user space Rx interrupt event.
+ * Enhanced multi-packet send function for ConnectX-5.
-* **Added support for Rx interrupts on mlx5 driver.**
+* **Update mlx4 PMD.**
- Rx queues can be armed with an interrupt which will trigger on the
- next packet arrival.
+ * Support for basic flow items and actions.
+ * Support device removal event.
* **Updated the sfc_efx driver.**
--
2.12.0
next reply other threads:[~2017-04-25 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 11:49 Shahaf Shuler [this message]
2017-04-26 9:01 ` Ferruh Yigit
2018-08-05 11:13 Shahaf Shuler
2018-08-08 22:55 ` 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=20170425114958.151811-1-shahafs@mellanox.com \
--to=shahafs@mellanox.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=olgas@mellanox.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).