From: Shahaf Shuler <shahafs@mellanox.com>
To: adrien.mazarguil@6wind.com, nelio.laranjeiro@6wind.com,
yskoh@mellanox.com, john.mcnamara@intel.com
Cc: dev@dpdk.org, olgas@mellanox.com
Subject: [dpdk-dev] [PATCH v2 2/2] doc: update mlx PMD required OFED version
Date: Sun, 4 Feb 2018 09:08:06 +0200 [thread overview]
Message-ID: <1a9b089fed79bf6b22e1ab81748eeaa5a543890b.1517727898.git.shahafs@mellanox.com> (raw)
In-Reply-To: <20180201114527.128941-1-shahafs@mellanox.com>
Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
---
On v2:
- Updated the OFED version for mlx4 guide as well.
---
doc/guides/nics/mlx4.rst | 2 +-
doc/guides/nics/mlx5.rst | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/guides/nics/mlx4.rst b/doc/guides/nics/mlx4.rst
index 88161781c..13cc6ec8a 100644
--- a/doc/guides/nics/mlx4.rst
+++ b/doc/guides/nics/mlx4.rst
@@ -219,7 +219,7 @@ Current RDMA core package and Linux kernel (recommended)
Mellanox OFED as a fallback
~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- `Mellanox OFED`_ version: **4.2**.
+- `Mellanox OFED`_ version: **4.2, 4.3**.
- firmware version: **2.42.5000** and above.
.. _`Mellanox OFED`: http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index a9e4bf51a..b2376363b 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -131,7 +131,7 @@ Limitations
- A multi segment packet must have less than 6 segments in case the Tx burst function
is set to multi-packet send or Enhanced multi-packet send. Otherwise it must have
less than 50 segments.
-- Count action for RTE flow is only supported in Mellanox OFED 4.2.
+- Count action for RTE flow is only supported in Mellanox OFED 4.2 and above.
- Flows with a VXLAN Network Identifier equal (or ends to be equal)
to 0 are not supported.
- VXLAN TSO and checksum offloads are not supported on VM.
@@ -392,7 +392,7 @@ RMDA Core with Linux Kernel
Mellanox OFED
^^^^^^^^^^^^^
-- Mellanox OFED version: **4.2**.
+- Mellanox OFED version: **4.2, 4.3**.
- firmware version:
- ConnectX-4: **12.21.1000** and above.
--
2.12.0
next prev parent reply other threads:[~2018-02-04 7:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 11:45 [dpdk-dev] [PATCH 1/2] doc: update mlx PMD release notes Shahaf Shuler
2018-02-01 11:45 ` [dpdk-dev] [PATCH 2/2] doc: update mlx5 required OFED version Shahaf Shuler
2018-02-04 7:06 ` [dpdk-dev] [PATCH v2 1/2] doc: update mlx PMD release notes Shahaf Shuler
2018-02-05 12:31 ` [dpdk-dev] [PATCH v3 " Shahaf Shuler
2018-02-05 13:12 ` Nélio Laranjeiro
2018-02-05 15:31 ` Adrien Mazarguil
2018-02-05 17:40 ` Ferruh Yigit
2018-02-05 12:31 ` [dpdk-dev] [PATCH v3 2/2] doc: update mlx5 required OFED version Shahaf Shuler
2018-02-05 13:12 ` Nélio Laranjeiro
2018-02-05 15:31 ` Adrien Mazarguil
2018-02-04 7:08 ` Shahaf Shuler [this message]
2018-02-05 7:44 ` [dpdk-dev] [PATCH v2 2/2] doc: update mlx PMD " Nélio Laranjeiro
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=1a9b089fed79bf6b22e1ab81748eeaa5a543890b.1517727898.git.shahafs@mellanox.com \
--to=shahafs@mellanox.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=olgas@mellanox.com \
--cc=yskoh@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).