From mboxrd@z Thu Jan 1 00:00:00 1970 From: Or Gerlitz Subject: Re: some failures with vxlan offloads.. Date: Wed, 29 Oct 2014 07:50:24 +0200 Message-ID: <54508020.1040305@mellanox.com> References: <544CF8E3.8070207@mellanox.com> <544FB5CA.2060003@mellanox.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Cc: "netdev@vger.kernel.org" To: Tom Herbert Return-path: Received: from eu1sys200aog132.obsmtp.com ([207.126.144.207]:33771 "EHLO eu1sys200aog132.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751226AbaJ2Fu3 (ORCPT ); Wed, 29 Oct 2014 01:50:29 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On 10/28/2014 5:36 PM, Tom Herbert wrote: >> I wonder if we have another bug somewhere... when both sides were offloaded, >> >it works even with the mlx4 bug, canyou explain that?is it possible that the >> >GRO stack somehow covers on the bug when both sides are offloaded and >> >GRO/VXLAN comes into play? >> > Look at the receive side. As I mentioned, if the device is returning > checksum-unnecessary and setting csum_level to 1 (inner checksum was > validated) then stack won't try to verify the outer checksum. So in > this case if outer checksum is incorrect nobody complains about it. OK, I'll look there. Anything that should worries us at that stack trace I sent in my initial email of this thread, or you think this is related to the mlx4 driver checksum bug? Or. >