From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Wu, Jingjing" <jingjing.wu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Xing, Beilei" <beilei.xing@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: add limitations for i40e PMD
Date: Mon, 26 Sep 2016 15:32:54 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE202622F77@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1474045575-31372-1-git-send-email-jingjing.wu@intel.com>
> -----Original Message-----
> From: Wu, Jingjing
> Sent: Friday, September 16, 2016 6:06 PM
> To: dev@dpdk.org
> Cc: Wu, Jingjing <jingjing.wu@intel.com>; Xing, Beilei
> <beilei.xing@intel.com>; Mcnamara, John <john.mcnamara@intel.com>
> Subject: [PATCH v2] doc: add limitations for i40e PMD
>
> 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>
>
> ...
>
> +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.
This paragraph is a little confusing. Perhaps you could simplify/clarify it.
next prev parent reply other threads:[~2016-09-26 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 2:17 [dpdk-dev] [PATCH] " Jingjing Wu
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 [this message]
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=B27915DBBA3421428155699D51E4CFE202622F77@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@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).