From: Ian Stokes <ian.stokes@intel.com>
To: dev@dpdk.org
Cc: Ian Stokes <ian.stokes@intel.com>
Subject: [dpdk-dev] [PATCH v2] doc: update GSG for i40e firmware version.
Date: Wed, 6 Jul 2016 11:29:31 +0100 [thread overview]
Message-ID: <1467800971-21140-1-git-send-email-ian.stokes@intel.com> (raw)
Update the 'High Performance of Small Packets on 40G NIC' section of the
GSG as the firmware version referenced for a NIC using the i40e driver was
firmware version 4.2.5 which is no longer validated. Instruct users to
consult release notes for current validated firmware versions.
Signed-off-by: Ian Stokes <ian.stokes@intel.com>
---
v1 -> v2
Specificy GSG in commit subject line.
Sepcify section in GSG that is updated in commit body.
Remove references to FVL in GSG, replace with 'NIC using i40e driver'.
---
doc/guides/linux_gsg/enable_func.rst | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/doc/guides/linux_gsg/enable_func.rst b/doc/guides/linux_gsg/enable_func.rst
index ec0e04d..6005932 100644
--- a/doc/guides/linux_gsg/enable_func.rst
+++ b/doc/guides/linux_gsg/enable_func.rst
@@ -183,8 +183,7 @@ High Performance of Small Packets on 40G NIC
As there might be firmware fixes for performance enhancement in latest version
of firmware image, the firmware update might be needed for getting high performance.
Check with the local Intel's Network Division application engineers for firmware updates.
-The base driver to support firmware version of FVL3E will be integrated in the next
-DPDK release, so currently the validated firmware version is 4.2.6.
+Users should consult the release notes specific to a DPDK release to identify the validated firmware version for a NIC using the i40e driver.
Use 16 Bytes RX Descriptor Size
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
1.7.4.1
next reply other threads:[~2016-07-06 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 10:29 Ian Stokes [this message]
2016-07-06 11:53 ` Mcnamara, John
2016-07-08 15:51 ` Bruce Richardson
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=1467800971-21140-1-git-send-email-ian.stokes@intel.com \
--to=ian.stokes@intel.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;
as well as URLs for NNTP newsgroup(s).