From: Heiner Kallweit <hkallweit1@gmail.com>
To: Peter Ceiley <peter@ceiley.net>,
Realtek linux nic maintainers <nic_swsd@realtek.com>
Cc: netdev@vger.kernel.org
Subject: Re: r8169 Driver - Poor Network Performance Since Kernel 4.19
Date: Mon, 28 Jan 2019 19:28:06 +0100 [thread overview]
Message-ID: <a123dc94-163a-36c1-5a20-a957f05430d3@gmail.com> (raw)
In-Reply-To: <CAMLO_R7Q6QCr7KX5goOvJ_BzDLU_tnw3UkMKzwDmL4C2BHubVA@mail.gmail.com>
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
next prev parent reply other threads:[~2019-01-28 18:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 11:13 r8169 Driver - Poor Network Performance Since Kernel 4.19 Peter Ceiley
2019-01-28 18:28 ` Heiner Kallweit [this message]
2019-01-28 22:10 ` Peter Ceiley
2019-01-29 6:16 ` Heiner Kallweit
2019-01-29 6:20 ` Peter Ceiley
2019-01-29 6:44 ` Heiner Kallweit
2019-01-30 9:59 ` Peter Ceiley
2019-01-30 19:15 ` Heiner Kallweit
2019-01-31 2:32 ` David Chang
2019-01-31 6:21 ` Heiner Kallweit
2019-01-31 6:35 ` Heiner Kallweit
2019-01-31 6:49 ` Heiner Kallweit
2019-01-31 7:23 ` David Chang
2019-01-31 12:09 ` Peter Ceiley
2019-01-31 18:28 ` Heiner Kallweit
2019-02-01 4:27 ` David Chang
2019-02-01 4:29 ` David Chang
2019-02-01 6:32 ` Heiner Kallweit
2019-02-02 12:25 ` Heiner Kallweit
2019-02-05 18:50 ` Heiner Kallweit
2019-02-05 18:53 ` Heiner Kallweit
2019-02-11 6:23 ` David Chang
2019-02-14 2:45 ` David Chang
2019-02-14 6:17 ` Heiner Kallweit
2019-02-15 2:51 ` David Chang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a123dc94-163a-36c1-5a20-a957f05430d3@gmail.com \
--to=hkallweit1@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=peter@ceiley.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).