From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 37FC95585 for ; Fri, 22 Jul 2016 04:10:34 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga103.fm.intel.com with ESMTP; 21 Jul 2016 19:10:34 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,402,1464678000"; d="scan'208,217";a="1021684374" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by orsmga002.jf.intel.com with ESMTP; 21 Jul 2016 19:10:32 -0700 Received: from FMSMSX109.amr.corp.intel.com (10.18.116.9) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 21 Jul 2016 19:10:32 -0700 Received: from shsmsx103.ccr.corp.intel.com (10.239.4.69) by fmsmsx109.amr.corp.intel.com (10.18.116.9) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 21 Jul 2016 19:10:31 -0700 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.147]) by SHSMSX103.ccr.corp.intel.com ([169.254.4.181]) with mapi id 14.03.0248.002; Fri, 22 Jul 2016 10:10:28 +0800 From: "Xu, Qian Q" To: "Yao, Lei A" , "Topel, Bjorn" , "Wu, Jingjing" CC: "dev@dpdk.org" , Thomas Monjalon Thread-Topic: l3fwd can't launch on VF when we use i40e Thread-Index: AdHjt+YHFX2SS93qQa2bdBe7fRyypgABbtlQ Date: Fri, 22 Jul 2016 02:10:28 +0000 Message-ID: <82F45D86ADE5454A95A89742C8D1410E032F7520@shsmsx102.ccr.corp.intel.com> References: <2DBBFF226F7CF64BAFCA79B681719D9502044162@shsmsx102.ccr.corp.intel.com> In-Reply-To: <2DBBFF226F7CF64BAFCA79B681719D9502044162@shsmsx102.ccr.corp.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] MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] l3fwd can't launch on VF when we use i40e 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: Fri, 22 Jul 2016 02:10:34 -0000 + dpdk.org mailing list. I also thought the patch to check port CRC strip t= hen make the port fail to start is not proper. For testpmd, we can use -crc-strip, but for l3fwd, we may need change code = to enable crc-strip, and for all application, we need change the code; this= is not acceptable. Users may think it's a bug of R16.07 since R16.04 didn't check that. From m= y view, crc-strip is not a "MUST" check for the port start. We can configur= e the value after the port start. Any thoughts? From: Yao, Lei A Sent: Friday, July 22, 2016 9:36 AM To: Topel, Bjorn Cc: Xu, Qian Q Subject: l3fwd can't launch on VF when we use i40e Hi, Bjorn This is lei who is running DPDK testing on VMware with 16.07 RC3. Now I met= one issue, after I enable SR-IOV on VMware with i40e related NIC, I can't = launch l3fwd example on VF because of this error info: i40evf_dev_configure(): VF can't disable HW CRC Strip. I see that you have submit following patch related to this scenario commit 1bbcc5d21129168a212e7d755751b0d4742d20d9 Author: Bj=F6rn T=F6pel Date: Fri Apr 22 07:39:22 2016 +0200 i40evf: report error for unsupported CRC stripping config On hosts running a non-DPDK PF driver, the VF has no means of changing the HW CRC strip setting for a RX queue. It's implicitly enabled. This patch checks if the host is running a non-DPDK PF kernel driver, and returns an error, if HW CRC stripping was not requested in the port configuration. Signed-off-by: Bj=F6rn T=F6pel Acked-by: Helin Zhang Do you know is there any way I can bypass this when I use l3fwd? I know whe= n we use testpmd, we can add --crc-strip enable to bypass this blocker. But= I don't know the method on l3fwd. Thanks. Best Regards Lei