From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 726C0C282CD for ; Mon, 28 Jan 2019 22:11:17 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 2542F2175B for ; Mon, 28 Jan 2019 22:11:17 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=ceiley-net.20150623.gappssmtp.com header.i=@ceiley-net.20150623.gappssmtp.com header.b="gFE85JGl" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726862AbfA1WLQ (ORCPT ); Mon, 28 Jan 2019 17:11:16 -0500 Received: from mail-ed1-f68.google.com ([209.85.208.68]:38793 "EHLO mail-ed1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726766AbfA1WLP (ORCPT ); Mon, 28 Jan 2019 17:11:15 -0500 Received: by mail-ed1-f68.google.com with SMTP id h50so14386695ede.5 for ; Mon, 28 Jan 2019 14:11:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ceiley-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=okk2BHcXdLKmdSv47yf6BwVj9wpVZYFcPh9YNwKfN+w=; b=gFE85JGl7ybX1tL1QUG/lxjo3CeslJ/CySVHmxa0YwIgdhI25WmwnZmEa1RUYB4Pej EKUePnoNEaTCA2e98WiLPEz7ucptchorQcAFvLfyyDULxKDtm9ozsMJpkS6qdfICDe1o 8hbmefu5WmFHahAxkRM8fNjGkZz76AsAfxfkb/wZ19K2EmAsFb08U5t259Hq85VqwEDA IW8lB49yxBFHndc6ifrUystoRr5Qmpb6Jxv8oHW5jfFO8sdfOk+CRdD1C+fmABuIEvP1 0o2Tlp0oJx5H+paUscCCMH6IbFbTWoIA6I4E/twSvdR77yPZ+yAbzDKmfhr1eo8wllSX Fbig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=okk2BHcXdLKmdSv47yf6BwVj9wpVZYFcPh9YNwKfN+w=; b=dxUkTv2ztV9SxbfrDkft3lXXR10PsJ3P1VK12VqQKKODc71Q5f2KgBRgf4GuE9MWeh c59A1y1n+nfO9sq9U79rhLWkil3qflY77U0dypQnAXZGmSUFovbTvcdyx8JLS0cSH7YW N8ZeZopcfb0o6r6wL1Uf5m+hhtv9ufbQbwlwILzgnG2PhoK6Bs3iYd7yyX5iQUyzgKkj qMTNL6QjANaeQHgspL21g40sKvUaFxenUqckmzaTgp4yikUNGuoXOR5urcEbPO9bxczN xRg+9ld8tKOzJCdEbA3z2DeOggMa9y3S6PpYzUAGg5k3KrvWBMvDOmxk27NpIniyB92F qXtQ== X-Gm-Message-State: AJcUukduuTbzygUiUn9YxpqXSQVdyD2Z2M1VGItxkISb23BWcLBMZeGk fy/y5K2Na/VqEQWU78IBaDv9bO60TD5Dr9W/fZ0EgA== X-Google-Smtp-Source: ALg8bN4nsAytF1xd9fHGiX3L2TFpyFURk9GbtkGM5m4FKmUQ4png5tMaQKp4PhwNvjDUXVhQndqK/s7M7k40O0Ou9fU= X-Received: by 2002:a17:906:4691:: with SMTP id a17mr20414275ejr.58.1548713473136; Mon, 28 Jan 2019 14:11:13 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Peter Ceiley Date: Tue, 29 Jan 2019 09:10:59 +1100 Message-ID: Subject: Re: r8169 Driver - Poor Network Performance Since Kernel 4.19 To: Heiner Kallweit , Realtek linux nic maintainers Cc: netdev@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Hi Heiner, Thanks for getting back to me. No, I don't use jumbo packets. Bandwidth is *generally* good, and iperf results to my NAS provide over 900 Mbits/s in both circumstances. The issue seems to appear when establishing a connection and is most notable, for example, on my mounted NFS shares where it takes seconds (up to 10's of seconds on larger directories) to list the contents of each directory. Once a transfer begins on a file, I appear to get good bandwidth. I'm unsure of the best scientific data to provide you in order to troubleshoot this issue. Running the following netstat -s |grep retransmitted shows a steady increase in retransmitted segments each time I list the contents of a remote directory, for example, running 'ls' on a directory containing 345 media files did the following using kernel 4.19.18: increased retransmitted segments by 21 and the 'time' command showed the following: real 0m19.867s user 0m0.012s sys 0m0.036s The same command shows no retransmitted segments running kernel 4.18.16 and 'time' showed: real 0m0.300s user 0m0.004s sys 0m0.007s ifconfig does not show any RX/TX errors nor dropped packets in either case. dmesg XID: [ 2.979984] r8169 0000:03:00.0 eth0: RTL8168g/8111g, f8:b1:56:fe:67:e0, XID 4c000800, IRQ 32 # lspci -vv 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c) Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- wrote: > > On 28.01.2019 12:13, Peter Ceiley wrote: > > Hi, > > > > I have been experiencing very poor network performance since Kernel > > 4.19 and I'm confident it's related to the r8169 driver. > > > > I have no issue with kernel versions 4.18 and prior. I am experiencing > > this issue in kernels 4.19 and 4.20 (currently running/testing with > > 4.20.4 & 4.19.18). > > > > If someone could guide me in the right direction, I'm happy to help > > troubleshoot this issue. Note that I have been keeping an eye on one > > issue related to loading of the PHY driver, however, my symptoms > > differ in that I still have a network connection. I have attempted to > > reload the driver on a running system, but this does not improve the > > situation. > > > > Using the proprietary r8168 driver returns my device to proper working order. > > > > lshw shows: > > description: Ethernet interface > > product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller > > vendor: Realtek Semiconductor Co., Ltd. > > physical id: 0 > > bus info: pci@0000:03:00.0 > > logical name: enp3s0 > > version: 0c > > serial: > > size: 1Gbit/s > > capacity: 1Gbit/s > > width: 64 bits > > clock: 33MHz > > capabilities: pm msi pciexpress msix vpd bus_master cap_list > > ethernet physical tp aui bnc mii fibre 10bt 10bt-fd 100bt 100bt-fd > > 1000bt-fd autonegotiation > > configuration: autonegotiation=on broadcast=yes driver=r8169 > > duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 ip=192.168.1.25 > > latency=0 link=yes multicast=yes port=MII speed=1Gbit/s > > resources: irq:19 ioport:d000(size=256) > > memory:f7b00000-f7b00fff memory:f2100000-f2103fff > > > > Kind Regards, > > > > Peter. > > > Hi Peter, > > the description "poor network performance" is quite vague, therefore: > > - Can you provide any measurements? > - iperf results before and after > - statistics about dropped packets (rx and/or tx) > - Do you use jumbo packets? > > Also help would be a "lspci -vv" output for the network card and > the dmesg output line with the chip XID. > > Heiner