From: Beilei Xing <beilei.xing@intel.com>
To: john.mcnamara@intel.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2] doc: add i40e update
Date: Mon, 8 Jan 2018 15:58:52 +0800 [thread overview]
Message-ID: <1515398332-78518-1-git-send-email-beilei.xing@intel.com> (raw)
In-Reply-To: <1515388390-46440-1-git-send-email-beilei.xing@intel.com>
Update release note to declare MPLSoUDP/MPLSoGRE/
GTP-U/GTP-C/PPPoE/PPPoL2TP steering support in i40e
driver.
Update i40e.rst to declare DDP support and input set
configuration.
Signed-off-by: Beilei Xing <beilei.xing@intel.com>
---
v2 changes:
- Add DDP support and input set configuration in i40e.rst.
doc/guides/nics/i40e.rst | 47 ++++++++++++++++++++++++++++++++++
doc/guides/rel_notes/release_18_02.rst | 31 ++++++++++++++++++++++
2 files changed, 78 insertions(+)
diff --git a/doc/guides/nics/i40e.rst b/doc/guides/nics/i40e.rst
index 2507d5f..789d6d6 100644
--- a/doc/guides/nics/i40e.rst
+++ b/doc/guides/nics/i40e.rst
@@ -65,6 +65,7 @@ Features of the I40E PMD are:
- Hot plug
- IEEE1588/802.1AS timestamping
- VF Daemon (VFD) - EXPERIMENTAL
+- Dynamic Device Personalization (DDP)
Prerequisites
@@ -374,6 +375,52 @@ configuration passed on the EAL command line.
The floating VEB functionality requires a NIC firmware version of 5.0
or greater.
+Dynamic Device Personalization (DDP)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The Intel® Ethernet Controller X*710 support a feature called "Dynamic Device
+Personalization (DDP)", which is used to configure hardware by downloading
+a profile to support protocols/filters which are not supported by default.
+The DDP functionality requires a NIC firmware version of 6.0 or greater.
+
+Current implementation supports MPLSoUDP/MPLSoGRE/GTP-C/GTP-U/PPPoE/PPPoL2TP,
+steering can be used with rte_flow API.
+
+Load a profile which supports MPLSoUDP/MPLSoGRE:
+
+.. code-block:: console
+
+ testpmd> ddp add 0 ./mpls.pkgo
+
+Delete a MPLS profile:
+
+.. code-block:: console
+
+ testpmd> ddp del 0 ./mpls.pkgo
+
+Get loaded DDP package info list:
+
+.. code-block:: console
+
+ testpmd> ddp get list 0
+
+Display information about a MPLS profile:
+
+.. code-block:: console
+
+ testpmd> ddp get info ./mpls.pkgo
+
+Input set configuration
+~~~~~~~~~~~~~~~~~~~~~~~
+Input set for any PCTYPE can be configured with user defined configuration,
+For example, to use only 48bit prefix for IPv6 src address for IPv6 TCP RSS:
+
+.. code-block:: console
+
+ testpmd> port config 0 pctype 43 hash_inset clear all
+ testpmd> port config 0 pctype 43 hash_inset set field 13
+ testpmd> port config 0 pctype 43 hash_inset set field 14
+ testpmd> port config 0 pctype 43 hash_inset set field 15
Limitations or Known issues
---------------------------
diff --git a/doc/guides/rel_notes/release_18_02.rst b/doc/guides/rel_notes/release_18_02.rst
index 621b8f5..b016c54 100644
--- a/doc/guides/rel_notes/release_18_02.rst
+++ b/doc/guides/rel_notes/release_18_02.rst
@@ -47,6 +47,37 @@ New Features
users. According to the device configuration, it will setup TX->RX loopback
link or not.
+* **Updated i40e driver to support MPLSoUDP/MPLSoGRE.**
+
+ Updated i40e PMD to support MPLSoUDP/MPLSoGRE with MPLSoUDP/MPLSoGRE
+ supporting profiles which can be programmed by dynamic device
+ personalization (DDP) process:
+
+ * Support cloud filer of MPLSoUDP/MPLSoGRE flow based on MPLS label.
+
+ This feature was implemented in release_17_05.
+
+* **Updated i40e driver to support GTP-C/GTP-U.**
+
+ Updated i40e PMD to support GTP-C/GTP-U with GTP-C/GTP-U supporting
+ profiles which can be programmed by dynamic device personalization (DDP)
+ process:
+
+ * Support RSS of GTP-C/GTP-U flow.
+ * Support flow director of GTP-C/GTP-U flow based on TEID.
+ * Support cloud filer of GTP-C/GTP-U flow based on TEID.
+
+ This feature was implemented in release_17_11, and only GTPv1 is supported.
+
+* **Updated i40e driver to support PPPoE/PPPoL2TP.**
+
+ Updated i40e PMD to support PPPoE/PPPoL2TP with PPPoE/PPPoL2TP supporting
+ profiles which can be programmed by dynamic device personalization (DDP)
+ process:
+
+ * Support RSS of PPPoE/PPPoL2TP flow based on user defined input set.
+ * Support FDIR of PPPoE/PPPoL2TP flow based on user defined input set.
+
API Changes
-----------
--
2.5.5
next prev parent reply other threads:[~2018-01-08 7:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 5:13 [dpdk-dev] [PATCH] " Beilei Xing
2018-01-08 5:37 ` Zhang, Helin
2018-01-08 7:58 ` Beilei Xing [this message]
2018-01-10 1:32 ` [dpdk-dev] [PATCH v2] " Zhang, Helin
2018-01-10 2:01 ` [dpdk-dev] [PATCH v3] " Beilei Xing
2018-01-10 2:44 ` Zhang, Helin
2018-01-16 22:01 ` Thomas Monjalon
2018-01-09 15:03 ` [dpdk-dev] [PATCH] " Mcnamara, John
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=1515398332-78518-1-git-send-email-beilei.xing@intel.com \
--to=beilei.xing@intel.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).