linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rod Webster <rod@vmn.com.au>
To: linux-rt-users@vger.kernel.org
Subject: Excessive network latency when using Realtek R8168/R8111 et al NIC
Date: Tue, 18 Apr 2023 13:23:12 +1000	[thread overview]
Message-ID: <CANV1gkc9KvkGNPkEsjXCiV4mUcdrrPcaQ1ueRri9ypjvJbU94g@mail.gmail.com> (raw)

Hi guys,
I hope this is the right place to report an issue

We are linuxcnc users and as such we are long term users of PREEMPT_RT
on x86 (and some other platforms)

A number of PC's in use by our members have recently been experiencing
excessive Real Time network latency since the 5.10 kernel and above.

We are excited to see this seems to have been mostly resolved with the
6.3 kernel compiled from patched kernel.org source.

But we are also experiencing excessive Real time network latency on
some NIC hardware, mostly with  Realtek NIC's in this list.

https://www.realtek.com/en/component/zoo/category/network-interface-controllers-10-100-1000m-gigabit-ethernet-pci-express-software
Many modern industrial PC's are using Realtek NIC drivers that cannot
be changed out so this is a problem for us.

It's our understanding that the R8169 kernel driver module should
provide support for this hardware. It does indeed do this but real
time network latency is unacceptable. Debian offers  a R8168-dkms
driver.  I understand it is being deprecated in favor of the R8169
kernel module driver.

Installing the R8168-dkms driver on the 6.3 kernel improves RT network
latency/jitter by 400% over the R8169 driver.

We are users not kernel developers. How can we escalate this issue so
acceptable RT performance is restored?

end
-Regards
-Rod Webster

             reply	other threads:[~2023-04-18  3:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18  3:23 Rod Webster [this message]
2023-04-28  8:51 ` Excessive network latency when using Realtek R8168/R8111 et al NIC Sebastian Andrzej Siewior
     [not found]   ` <CANV1gkcr4jBUY-iH-iJJPdrVMp+1Nq1YrNPONferMC1AutJgkg@mail.gmail.com>
2023-04-28 13:12     ` Sebastian Andrzej Siewior
2023-04-28 21:37       ` Rod Webster
2023-04-29  1:00         ` Rod Webster
2023-05-16 10:59         ` Sebastian Andrzej Siewior
     [not found]           ` <CANV1gkftrZvhUhXV-mJ-mYmsue3ER33cXCNmVD1bGAc6TmTHuA@mail.gmail.com>
     [not found]             ` <CANV1gkfsAfDt76=STFrekQA4M6sfVKyq7bujA=Tu+S6k+EGYcg@mail.gmail.com>
2023-05-19  8:37               ` Sebastian Andrzej Siewior
2023-05-19 11:41                 ` Rod Webster
2023-05-22  9:32                   ` Sebastian Andrzej Siewior
2023-05-22 10:06                     ` Rod Webster
2023-05-22 14:45                       ` Marcelo Tosatti
2023-05-22 20:02                         ` Rod Webster
2023-05-22 20:37                           ` Peter Wallace
2023-05-22 20:50                             ` Rod Webster
2023-05-23 23:21                             ` Marcelo Tosatti
2023-05-24 14:09                               ` Peter Wallace
2023-05-23 23:04                           ` Marcelo Tosatti
2023-05-24  9:37                             ` Stephane ANCELOT

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=CANV1gkc9KvkGNPkEsjXCiV4mUcdrrPcaQ1ueRri9ypjvJbU94g@mail.gmail.com \
    --to=rod@vmn.com.au \
    --cc=linux-rt-users@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;
as well as URLs for NNTP newsgroup(s).