From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olivier MATZ Subject: Re: [PATCH v3 0/3] enhance TX checksum command and csum forwarding engine Date: Wed, 21 Jan 2015 18:13:06 +0100 Message-ID: <54BFDE22.9050300@6wind.com> References: <1418173403-30202-1-git-send-email-jijiang.liu@intel.com> <54AFB13E.2080200@6wind.com> <1ED644BD7E0A5F4091CF203DAFB8E4CC01DA85A1@SHSMSX101.ccr.corp.intel.com> <54B3B35A.5030803@6wind.com> <1ED644BD7E0A5F4091CF203DAFB8E4CC01DA8E36@SHSMSX101.ccr.corp.intel.com> <54B4EB92.40209@6wind.com> <1ED644BD7E0A5F4091CF203DAFB8E4CC01DB0789@SHSMSX101.ccr.corp.intel.com> <2601191342CEEE43887BDE71AB977258213D4FCF@irsmsx105.ger.corp.intel.com> <54B94A18.5030700@6wind.com> <2601191342CEEE43887BDE71AB977258213DCD25@irsmsx105.ger.corp.intel.com> <54BD16F1.6050409@6wind.com> <2601191342CEEE43887BDE71AB977258213DDF46@irsmsx105.ger.corp.intel.com> <54BE4C70.7050406@6wind.com> <2601191342CEEE43887BDE71AB977258213DE5FB@irsmsx105.ger.corp.intel.com> <54BE9B56.7050108@6wind.com> <1ED644BD7E0A5F4091CF203DAFB8E4CC01DB55DB@SHSMSX101.ccr.corp.intel.com> <54BFC4D6.2010903@6wind.com> <2601191342CEEE43887BDE71AB977258213DEA1E@irsmsx105.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: "dev-VfR2kkLFssw@public.gmane.org" To: "Ananyev, Konstantin" , "Liu, Jijiang" Return-path: In-Reply-To: <2601191342CEEE43887BDE71AB977258213DEA1E-pww93C2UFcwu0RiL9chJVbfspsVTdybXVpNB7YpNyf8@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" Hi Konstantin, On 01/21/2015 05:28 PM, Ananyev, Konstantin wrote: >> I added the support of Ether over GRE, IP over GRE and IP over IP >> tunnels in csumonly to do the test. I ask the csum forward engine >> to calculate inner IP+TCP checksums, and outer IP (case 6 in [1]). >> Here are the results: >> >> 1/ When I use I40E_TXD_CTX_UDP_TUNNELING: >> - vxlan: all checksums ok >> - eth over gre: all checksums ok >> - ip over gre: not transmitted by hw >> - ip over ip: all checksums wrong (set to 0 by hw) >> >> 2/ When I use I40E_TXD_CTX_GRE_TUNNELING: >> - vxlan: checksums ok >> - eth over gre: all checksums ok >> - ip over gre: all checksums ok >> - ip over ip: all checksums wrong (set to 0 by hw) >> >> 3/ When I use 00b: >> - vxlan: all checksums ok >> - eth over gre: all checksums ok >> - ip over gre: all checksums ok >> - ip over ip: checksums wrong (set to 0 by hw) > > Wow, so there is absolutely no difference in results for L4TUNT=2(GRE) and L4TUNT=0, right? > And IP over IP doesn't work at all? Right. I probably missed something in i40e driver. The application seems to fill the mbuf properly. > I suppose you set L4TUNLEN as described in spec for each case, right? I think so. > That looks really weird to me and as I can see completely contradicts with what spec. > I suppose we'll need to reproduce all that tests on our HW too. > Could you send to us a patch with your changes, so we can try same thing? > Or just a dump of TDD and TCD values for each case. Sure, I'm going to send all my code and tests in a RFC patchset in a few minutes. By the way, I'm off tomorrow, I won't be able to answer. Regards, Olivier