From: Jingjing Wu <jingjing.wu@intel.com>
To: john.mcnamara@intel.com
Cc: dev@dpdk.org, jingjing.wu@intel.com, helin.zhang@intel.com
Subject: [dpdk-dev] [PATCH] doc: add limitations for i40e PMD
Date: Tue, 6 Sep 2016 10:17:08 +0800 [thread overview]
Message-ID: <1473128228-837-1-git-send-email-jingjing.wu@intel.com> (raw)
This patch adds "Limitations or Known issues" section for
i40e PMD, including two items:
1. MPLS packet classification on X710/XL710
2. 16 Byte Descriptor cannot be used on DPDK VF
Signed-off-by: Jingjing Wu <jingjing.wu@intel.com>
---
doc/guides/nics/i40e.rst | 33 +++++++++++++++++++++++++++++++++
1 file changed, 33 insertions(+)
diff --git a/doc/guides/nics/i40e.rst b/doc/guides/nics/i40e.rst
index 4d12b10..6df0f7a 100644
--- a/doc/guides/nics/i40e.rst
+++ b/doc/guides/nics/i40e.rst
@@ -411,3 +411,36 @@ configuration passed on the EAL command line.
The floating VEB functionality requires a NIC firmware version of 5.0
or greater.
+
+
+Limitations or Known issues
+---------------------------
+
+MPLS packet classification on X710/XL710
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Before NIC firmware version of 5.0, MPLS packet cannot be recognized by NIC.
+The L2 Payload flow type in flow director can be used to classify MPLS packet
+by the command in testpmd like:
+
+ testpmd> flow_director_filter 0 mode IP add flow l2_payload ether \
+ 0x8847 flexbytes () fwd pf queue <N> fd_id <M>
+
+In the NIC firmware whose version is 5.0 or greater, very limited MPLS support
+is added: Native MPLS skip is implemented, that is, packet type can be
+recognized like MPLS header is skipped, while no new packet type and no more
+meta data is extracted from MPLS header. With this change, L2 Payload flow
+type in flow director cannot be used to classify MPLS packet as previous.
+Meanwhile, Ethertype filter can be used to classify MPLS packet by the command
+in testpmd like:
+
+ testpmd> ethertype_filter 0 add mac_ignr 00:00:00:00:00:00 ethertype \
+ 0x8847 fwd queue <M>
+
+16 Byte Descriptor cannot be used on DPDK VF
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+If Linux i40e kerel driver is used as host driver, while DPDK i40e PMD is used
+as VF driver, DPDK cannot choose 16 byte descriptor receive descriptor. That
+is to say, user should keep "CONFIG_RTE_LIBRTE_I40E_16BYTE_RX_DESC=n" in config
+file.
--
2.4.11
next reply other threads:[~2016-09-06 2:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 2:17 Jingjing Wu [this message]
2016-09-13 9:48 ` Xing, Beilei
2016-09-16 17:06 ` [dpdk-dev] [PATCH v2] " Jingjing Wu
2016-09-26 15:32 ` Mcnamara, John
2016-09-30 6:46 ` [dpdk-dev] [PATCH v3] " Jingjing Wu
2016-09-30 15:09 ` Mcnamara, John
2016-10-12 15:17 ` 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=1473128228-837-1-git-send-email-jingjing.wu@intel.com \
--to=jingjing.wu@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--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).