From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 4D875530F for ; Tue, 13 Sep 2016 11:48:59 +0200 (CEST) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga105.jf.intel.com with ESMTP; 13 Sep 2016 02:48:58 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,328,1470726000"; d="scan'208";a="167592999" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by fmsmga004.fm.intel.com with ESMTP; 13 Sep 2016 02:48:58 -0700 Received: from shsmsx103.ccr.corp.intel.com (10.239.4.69) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 13 Sep 2016 02:48:57 -0700 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.91]) by SHSMSX103.ccr.corp.intel.com ([169.254.4.102]) with mapi id 14.03.0248.002; Tue, 13 Sep 2016 17:48:56 +0800 From: "Xing, Beilei" To: "Wu, Jingjing" , "Mcnamara, John" CC: "dev@dpdk.org" , "Wu, Jingjing" , "Zhang, Helin" Thread-Topic: [dpdk-dev] [PATCH] doc: add limitations for i40e PMD Thread-Index: AQHSB+T0fg9KJ6dFbE2EkTaGt0uiTaB3NvFQ Date: Tue, 13 Sep 2016 09:48:55 +0000 Message-ID: <94479800C636CB44BD422CB454846E012E938DFE@SHSMSX101.ccr.corp.intel.com> References: <1473128228-837-1-git-send-email-jingjing.wu@intel.com> In-Reply-To: <1473128228-837-1-git-send-email-jingjing.wu@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH] doc: add limitations for i40e PMD X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Sep 2016 09:48:59 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jingjing Wu > Sent: Tuesday, September 6, 2016 10:17 AM > To: Mcnamara, John > Cc: dev@dpdk.org; Wu, Jingjing ; Zhang, Helin > > Subject: [dpdk-dev] [PATCH] doc: add limitations for i40e PMD >=20 > This patch adds "Limitations or Known issues" section for i40e PMD, inclu= ding > two items: > 1. MPLS packet classification on X710/XL710 2. 16 Byte Descriptor cannot = be > used on DPDK VF >=20 > Signed-off-by: Jingjing Wu > --- > doc/guides/nics/i40e.rst | 33 +++++++++++++++++++++++++++++++++ > 1 file changed, 33 insertions(+) >=20 > 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. >=20 > The floating VEB functionality requires a NIC firmware version of 5.0 o= r > 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 fd_id > + > +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 pa= cket > 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 > + > +16 Byte Descriptor cannot be used on DPDK VF > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > + > +If Linux i40e kerel driver is used as host driver, while DPDK i40e PMD one typo: kerel -> kernel > +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=3Dn" in config file. > -- > 2.4.11