From: Olga Shern <olgas@mellanox.com>
To: dev@dpdk.org
Subject: [PATCH 2/2] release_2_2.rst: add mlx4 and mlx5 known issues
Date: Sun, 13 Dec 2015 00:13:25 +0200 [thread overview]
Message-ID: <1449958406-24994-3-git-send-email-olgas@mellanox.com> (raw)
In-Reply-To: <1449958406-24994-1-git-send-email-olgas@mellanox.com>
Signed-off-by: Olga Shern <olgas@mellanox.com>
---
doc/guides/rel_notes/release_2_2.rst | 13 +++++++++++++
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/doc/guides/rel_notes/release_2_2.rst b/doc/guides/rel_notes/release_2_2.rst
index c3ff086..4f393cf 100644
--- a/doc/guides/rel_notes/release_2_2.rst
+++ b/doc/guides/rel_notes/release_2_2.rst
@@ -284,6 +284,19 @@ Known Issues
As the l3fwd example application requires this info, the i40e vector
driver must be disabled to benefit of the packet type with i40e.
+* **Mellanox PMDs (mlx4 & mlx5):**
+
+ * PMDs do not support DPDK integrated shared library.
+
+ * There is performance degradation for small packets when PMD
+ is compiled with SGE_WR_N = 4 compared to the performance when SGE_WR_N = 1.
+ If scattered packets are not used it is recomended
+ to compile PMD with SGE_WR_N = 1.
+
+ **mlx4:**
+
+ * When a Multicast or Broadcast packet is sent to the SR-IOV VF,
+ it is returned back to the port.
API Changes
-----------
--
1.7.8.2
next prev parent reply other threads:[~2015-12-12 22:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 22:13 [PATCH 0/2] *** Updated release_2_2.rst with mlx4 and mlx5 information *** Olga Shern
2015-12-12 22:13 ` [PATCH 1/2] release_2_2.rst: add mlx4 new features and bug fixes Olga Shern
2015-12-12 22:13 ` Olga Shern [this message]
2015-12-14 0:11 ` [PATCH 0/2] *** Updated release_2_2.rst with mlx4 and mlx5 information *** 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=1449958406-24994-3-git-send-email-olgas@mellanox.com \
--to=olgas@mellanox.com \
--cc=dev@dpdk.org \
/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