From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: John McNamara <john.mcnamara@intel.com>
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 2/2] doc: add mlx4 release notes to DPDK 2.1.0
Date: Tue, 11 Aug 2015 16:42:45 +0200 [thread overview]
Message-ID: <1439304165-28438-3-git-send-email-adrien.mazarguil@6wind.com> (raw)
In-Reply-To: <1439304165-28438-1-git-send-email-adrien.mazarguil@6wind.com>
Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
---
doc/guides/rel_notes/release_2_1.rst | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/doc/guides/rel_notes/release_2_1.rst b/doc/guides/rel_notes/release_2_1.rst
index c39418c..00edd4b 100644
--- a/doc/guides/rel_notes/release_2_1.rst
+++ b/doc/guides/rel_notes/release_2_1.rst
@@ -38,12 +38,32 @@ New Features
* TODO.
+* Mellanox ConnectX-3 PMD (mlx4) enhancements.
+
+ * Support Mellanox OFED 3.0.
+
+ * Improved performance for both RX and TX operations.
+
+ * Better link status information.
+
+ * Outer L3/L4 checksum offload support.
+
+ * Inner L3/L4 checksum offload support for VXLAN.
Resolved Issues
---------------
* TODO.
+* Mellanox ConnectX-3 PMD (mlx4) bugfixes.
+
+ * Multiple VLAN filters support.
+
+ * Compilation on 32 bit platforms.
+
+ * Possible crash in case of mbuf allocation failure.
+
+ * Compilation as a shared library.
Known Issues
------------
--
2.1.0
next prev parent reply other threads:[~2015-08-11 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 14:42 [dpdk-dev] [PATCH 0/2] add mlx4 release notes Adrien Mazarguil
2015-08-11 14:42 ` [dpdk-dev] [PATCH 1/2] doc: add missing release notes for mlx4 availability in DPDK 2.0.0 Adrien Mazarguil
2015-08-12 6:38 ` Mcnamara, John
2015-08-11 14:42 ` Adrien Mazarguil [this message]
2015-08-12 6:38 ` [dpdk-dev] [PATCH 2/2] doc: add mlx4 release notes to DPDK 2.1.0 Mcnamara, John
2015-08-17 17:36 ` [dpdk-dev] [PATCH 0/2] add mlx4 release notes 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=1439304165-28438-3-git-send-email-adrien.mazarguil@6wind.com \
--to=adrien.mazarguil@6wind.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).