mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Holger Hoffstätte" <holger@applied-asynchrony.com>
To: Jonathan Woithe <jwoithe@atrad.com.au>, netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: r8169 regression: UDP packets dropped intermittantly
Date: Mon, 18 Dec 2017 14:38:53 +0100	[thread overview]
Message-ID: <c47cfb79-afb9-e39b-4861-7c534c55bb70@applied-asynchrony.com> (raw)
In-Reply-To: <20171218054951.GJ17747@marvin.atrad.com.au>

On 12/18/17 06:49, Jonathan Woithe wrote:
> Resend to netdev.  LKML CCed in case anyone in the wider kernel community
> can suggest a way forward.  Please CC responses if replying only to LKML.
> 
> It seems that this 4+ year old regression in the r8169 driver (documented in
> this thread on netdev beginning on 9 March 2013) will never be fixed,
> despite the identification of the commit which broke it.  Cards using this
> driver will therefore remain unusable for certain workloads utilising UDP.
(snip)

Hi,

Since I've seen your postings several times now with no comment or resolution
I've decided to try your reproducer on my own systems. In short, I cannot
reproduce any packet loss, despite having 2 (cheap) 1Gb switches between the
two machines. Both are running 4.14.7.

Both NICs are onboard PCIe and identify as:
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)

$ethtool -i eth0
driver: r8169
version: 2.3LK-NAPI
firmware-version: rtl8168e-3_0.0.4 03/27/12
..

Both machines are from 2012, so quite dated already. Nevertheless your
reproducer runs forever and all I see is 6 bytes request, 14 bytes response,
with no drops. Not one. I tried in both directions - no difference.

I realize this doesn't actually solve your immediate problem, but it is
nevertheless an indicator that whatever you have been observing is caused
by something else.

regards,
Holger

  reply	other threads:[~2017-12-18 13:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-18  5:49 Jonathan Woithe
2017-12-18 13:38 ` Holger Hoffstätte [this message]
2017-12-18 22:32   ` Jonathan Woithe
2017-12-19  5:45     ` Jonathan Woithe
2017-12-19 12:25       ` Michal Kubecek
2017-12-20  5:20         ` Jonathan Woithe
2018-01-15  6:56           ` Jonathan Woithe
2018-10-22  0:01             ` Jonathan Woithe

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=c47cfb79-afb9-e39b-4861-7c534c55bb70@applied-asynchrony.com \
    --to=holger@applied-asynchrony.com \
    --cc=jwoithe@atrad.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®