From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 34FCB3772 for ; Wed, 9 Nov 2016 14:09:45 +0100 (CET) Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga102.fm.intel.com with ESMTP; 09 Nov 2016 05:09:45 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,614,1473145200"; d="scan'208";a="29334881" Received: from rmitura-mobl1.ger.corp.intel.com (HELO [10.252.24.154]) ([10.252.24.154]) by orsmga004.jf.intel.com with ESMTP; 09 Nov 2016 05:09:43 -0800 To: "Zhang, Helin" , "Ananyev, Konstantin" , "dev@dpdk.org" References: <20161109082341.19825-1-bjorn.topel@intel.com> <2601191342CEEE43887BDE71AB9772583F0D2F6C@irsmsx105.ger.corp.intel.com> <5ad83b54-f13b-787e-c056-958f5cb8bd61@intel.com> <2601191342CEEE43887BDE71AB9772583F0D2FD9@irsmsx105.ger.corp.intel.com> Cc: "Xu, Qian Q" , "Yao, Lei A" , "Wu, Jingjing" , "thomas.monjalon@6wind.com" From: =?UTF-8?B?QmrDtnJuIFTDtnBlbA==?= Message-ID: Date: Wed, 9 Nov 2016 14:09:42 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH] examples/l3fwd: force CRC stripping for i40evf 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: Wed, 09 Nov 2016 13:09:46 -0000 Björn/Konstantin wrote: >> Finally, why doesn't l3fwd have the CRC stripped? > > I don’t know any good reason for that for l3fwd or any other sample > app. I think it is just a 'historical' reason. Ok! Then I'd suggest changing the l3fwd default to actually *strip* CRC instead of not doing it. Lei, any comments? Helin wrote: > Yes, i40e driver changed a little bit on that according to the > review comments during implementation, comparing to igb and ixgbe. > I'd suggest to re-invesitgate if we can do the similar thing in igb > and ixgbe driver. Good. Let's do that! > Any critical issue now? Or just an improvement comments? Not from my perspective. The issue is that Lei needs some kind of work-around for l3fwd with i40evf, so I'll let Lei comment on how critical it is. Björn