From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Fainelli Subject: Re: [Intel-wired-lan] NFS over NAT causes e1000e transmit hangs Date: Wed, 19 Apr 2017 14:15:34 -0700 Message-ID: <50732fb0-d2b6-9395-d982-6eca8c09aedd@gmail.com> References: <42af0e78-3107-1605-f8e1-d73a8c441ff0@gmail.com> <1492542204.10587.138.camel@edumazet-glaptop3.roam.corp.google.com> <9fa24846-3a2d-26d3-2963-f5e6ec6808a5@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org To: "Neftin, Sasha" , Eric Dumazet Return-path: Received: from mail-yw0-f196.google.com ([209.85.161.196]:34539 "EHLO mail-yw0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S967344AbdDSVPg (ORCPT ); Wed, 19 Apr 2017 17:15:36 -0400 Received: by mail-yw0-f196.google.com with SMTP id u70so3837548ywe.1 for ; Wed, 19 Apr 2017 14:15:36 -0700 (PDT) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On 04/19/2017 01:52 AM, Neftin, Sasha wrote: > On 4/18/2017 22:05, Florian Fainelli wrote: >> On 04/18/2017 12:03 PM, Eric Dumazet wrote: >>> On Tue, 2017-04-18 at 11:18 -0700, Florian Fainelli wrote: >>>> Hi, >>>> >>>> I am using NFS over a NAT with two e1000e adapters and with eth1 being >>>> the LAN interface and eth0 the WAN interface. The kernel is Ubuntu's >>>> 16.10 kernel: 4.8.0-46-generic. The device doing NAT over NFS is just >>>> mounting a remote folder and doing normal execution/file accesses. It's >>>> enough to untar a file from this device onto a NFS share to expose the >>>> problem. >>>> >>>> The transmit hangs look like the ones below, doing a rmmod/insmod does >>>> not help eliminated the problem, nor does a power cycle. Stopping the >>>> NFS over NAT definitively does let the adapter recover. >>> Is this NFS over TCP or UDP ? >> This is NFS over TCP mounted with the following: >> >> type nfs >> (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=2049,timeo=70,retrans=3,sec=sys,local_lock=none,addr=X.X.X.X) >> >> >> Thanks Eric! > > Please, try disable TCP segmentation offload: ethtool -K tso off. I am not able to reproduce the hangs with TSO turned off. Is there a specific patch you would want me to try? -- Florian From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Fainelli Date: Wed, 19 Apr 2017 14:15:34 -0700 Subject: [Intel-wired-lan] NFS over NAT causes e1000e transmit hangs In-Reply-To: References: <42af0e78-3107-1605-f8e1-d73a8c441ff0@gmail.com> <1492542204.10587.138.camel@edumazet-glaptop3.roam.corp.google.com> <9fa24846-3a2d-26d3-2963-f5e6ec6808a5@gmail.com> Message-ID: <50732fb0-d2b6-9395-d982-6eca8c09aedd@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: intel-wired-lan@osuosl.org List-ID: On 04/19/2017 01:52 AM, Neftin, Sasha wrote: > On 4/18/2017 22:05, Florian Fainelli wrote: >> On 04/18/2017 12:03 PM, Eric Dumazet wrote: >>> On Tue, 2017-04-18 at 11:18 -0700, Florian Fainelli wrote: >>>> Hi, >>>> >>>> I am using NFS over a NAT with two e1000e adapters and with eth1 being >>>> the LAN interface and eth0 the WAN interface. The kernel is Ubuntu's >>>> 16.10 kernel: 4.8.0-46-generic. The device doing NAT over NFS is just >>>> mounting a remote folder and doing normal execution/file accesses. It's >>>> enough to untar a file from this device onto a NFS share to expose the >>>> problem. >>>> >>>> The transmit hangs look like the ones below, doing a rmmod/insmod does >>>> not help eliminated the problem, nor does a power cycle. Stopping the >>>> NFS over NAT definitively does let the adapter recover. >>> Is this NFS over TCP or UDP ? >> This is NFS over TCP mounted with the following: >> >> type nfs >> (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=2049,timeo=70,retrans=3,sec=sys,local_lock=none,addr=X.X.X.X) >> >> >> Thanks Eric! > > Please, try disable TCP segmentation offload: ethtool -K tso off. I am not able to reproduce the hangs with TSO turned off. Is there a specific patch you would want me to try? -- Florian