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.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, 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 5E411C282C8 for ; Mon, 28 Jan 2019 18:28:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 301C12175B for ; Mon, 28 Jan 2019 18:28:16 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="aLWqNor+" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727577AbfA1S2O (ORCPT ); Mon, 28 Jan 2019 13:28:14 -0500 Received: from mail-wr1-f45.google.com ([209.85.221.45]:35421 "EHLO mail-wr1-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727232AbfA1S2O (ORCPT ); Mon, 28 Jan 2019 13:28:14 -0500 Received: by mail-wr1-f45.google.com with SMTP id 96so19251303wrb.2 for ; Mon, 28 Jan 2019 10:28:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=niFUU+pMzeOAk8+gxvuQeQTLww0Lo90rKwE3mowQN28=; b=aLWqNor+Y8Ezy5AFkRr1vZTOJ06/zjT3M1iSJANPWOJGU0OsseXZTWIBqD7R91YbJB KWEs63dM6o0OAVqddIV77LTwSjmWtjC7cGZlcflfxGoRaiUex/z1Zj9uzKQWCf445C+F 830Hm96Fw/q+561ZGC8tpzm5dPCt7yhawxsnP226thGssgWi4lEm2mEXyY6I/dBuj98X /6lOPlWKb49OgVNT3gCNKj8Rp2Kn59psSnYHBnrL27VTG6rN6vWRRVFBGE9G/YUuUp6y aI5DuIbzl+lOanPa+3AWPJKPrd+XJZb58y7SyAymjIbQu97RexXz9A7tJcDdAmuRcaLv 1QHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=niFUU+pMzeOAk8+gxvuQeQTLww0Lo90rKwE3mowQN28=; b=CEy9tR3uNhBNZOa62NwNZbzPZumXOAR5RapcsQQ5EBVoRZeRACOKtu7nCR9saT5e4J X0f7KRZNicsAheSj817pX87Zt+cccpl5BZOeWc34iAKhNRFupViVPH7FxdBpLSGSvnRO 5s26djdxVFvlwUPoHNFgAiduikm2TR2LM3gXOizBHYJ6EQRRj9Ogt7bSkwjixLVJMY7m hcd219L2lgdgoljvr5T8fZKnsVpEaGXvgufKKRnaPp4meEw31dPpEDi6ABoeYmPASc1H KB257RpL2lh+NTttxsqvOJbyxUKFAx2b/1uDEH4NxaWweTPt5C7jZGlCVcjlMFJjXilR s5ug== X-Gm-Message-State: AJcUukdcaONZEJHLB2LMxGExJkRg9i6Qb0yHTVsbfm+kTmd3qMdM2pBn I998U/JRTnykZb+k0aLQi+ayJI3Y X-Google-Smtp-Source: ALg8bN5AHF/y1u14TXmKtjfhbggsKykXpoyaDhDpcOjGQK+w5P85706h6fyeCgpoELF/40I5gfWCBw== X-Received: by 2002:adf:8264:: with SMTP id 91mr21979769wrb.312.1548700092368; Mon, 28 Jan 2019 10:28:12 -0800 (PST) Received: from ?IPv6:2003:ea:8bf1:e200:2c9c:e1a3:b321:9449? (p200300EA8BF1E2002C9CE1A3B3219449.dip0.t-ipconnect.de. [2003:ea:8bf1:e200:2c9c:e1a3:b321:9449]) by smtp.googlemail.com with ESMTPSA id 200sm251498wmw.31.2019.01.28.10.28.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 28 Jan 2019 10:28:11 -0800 (PST) Subject: Re: r8169 Driver - Poor Network Performance Since Kernel 4.19 To: Peter Ceiley , Realtek linux nic maintainers Cc: netdev@vger.kernel.org References: From: Heiner Kallweit Message-ID: Date: Mon, 28 Jan 2019 19:28:06 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org 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