From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id C86525588 for ; Thu, 12 Jan 2017 14:30:41 +0100 (CET) Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga104.jf.intel.com with ESMTP; 12 Jan 2017 05:30:40 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,349,1477983600"; d="scan'208";a="52188221" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by orsmga005.jf.intel.com with ESMTP; 12 Jan 2017 05:30:40 -0800 Received: from fmsmsx115.amr.corp.intel.com (10.18.116.19) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 12 Jan 2017 05:30:39 -0800 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by fmsmsx115.amr.corp.intel.com (10.18.116.19) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 12 Jan 2017 05:30:39 -0800 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.88]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.204]) with mapi id 14.03.0248.002; Thu, 12 Jan 2017 21:30:37 +0800 From: "Chen, Jing D" To: "Yigit, Ferruh" , Shaham Fridenberg , "dev@dpdk.org" Thread-Topic: [dpdk-dev] fm10k pmd limitations Thread-Index: AdJVMrxHvRIoKkbATK6TXPLlCB338AAFOyWwBdAQvQAAE+cosA== Date: Thu, 12 Jan 2017 13:30:35 +0000 Message-ID: <4341B239C0EFF9468EE453F9E9F4604D3C5DA797@shsmsx102.ccr.corp.intel.com> References: <2E654B490240B7449C846A96A8D8FE0C0116617B08@ILMB1.corp.radware.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYTQ1NDc2MjMtNTlkYi00NzA1LWJjNDItMDg2OGRlYTBmNjcyIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6ImFZMnVKdUZETzNyZDVFVjVKYjdaeVpObHR3UlZBUUZzaFR3ZVhSSFU5ckk9In0= x-ctpclassification: CTP_IC 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] fm10k pmd limitations X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 13:30:42 -0000 > -----Original Message----- > From: Yigit, Ferruh > Sent: Thursday, January 12, 2017 7:57 PM > To: Shaham Fridenberg ; dev@dpdk.org > Cc: Chen, Jing D > Subject: Re: [dpdk-dev] fm10k pmd limitations >=20 > On 12/13/2016 1:49 PM, Shaham Fridenberg wrote: > > Hey guys, > > > > I'm using dpdk 16.4 and fm10k card. According to the code, there's no > support for disabling vlan stripping and VLAN QinQ in pmd fm10k. > > Does anybody know why? If there's any way to work-around it, or when is= a > behavior change expected? Yes, HW will always strip it and driver will copy it into=20 (struct rte_mbuf *)mbuf->vlan_tci.=20 > > I need my VF to receive the packets with the VLAN headers. VF can read from rte_mbuf. > > Even if it's possible to change this configurations through the linux k= ernel > fm10k driver? > > > > Thanks! > > >=20 > CC fm10k maintainer: Jing Chen