From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cong Wang Subject: Re: [Patch net v2] mlx5: fixup checksum for short ethernet frame padding Date: Wed, 28 Nov 2018 19:53:11 -0800 Message-ID: References: <20181128061013.3885-1-xiyou.wangcong@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Cc: Linux Kernel Network Developers , Saeed Mahameed To: Eric Dumazet Return-path: Received: from mail-pf1-f195.google.com ([209.85.210.195]:36413 "EHLO mail-pf1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727022AbeK2O5T (ORCPT ); Thu, 29 Nov 2018 09:57:19 -0500 Received: by mail-pf1-f195.google.com with SMTP id b85so342238pfc.3 for ; Wed, 28 Nov 2018 19:53:23 -0800 (PST) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Wed, Nov 28, 2018 at 7:50 PM Eric Dumazet wrote: > > On Wed, Nov 28, 2018 at 7:40 PM Cong Wang wrote: > > > > On Wed, Nov 28, 2018 at 4:07 PM Eric Dumazet wrote: > > > > > > A NIC is supposed to deliver frames, even the ones that 'seem' bad. > > > > A quick test shows this is not the case for mlx5. > > > > With the trafgen script you gave to me, with tot_len==40, the dest host > > could receive all the packets. Changing tot_len to 80, tcpdump could no > > longer see any packet. (Both sender and receiver are mlx5.) > > > > So, packets with tot_len > skb->len are clearly dropped before tcpdump > > could see it, that is likely by mlx5 hardware. > > Or a router, or a switch. > > Are your two hosts connected back to back ? Both should be plugged into a same switch. I fail to see why a switch could parse IP header as the packet is nothing of interest, like a IGMP snooping.