linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rod Webster <rod@vmn.com.au>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	linux-rt-users@vger.kernel.org
Subject: Re: Excessive network latency when using Realtek R8168/R8111 et al NIC
Date: Mon, 22 May 2023 20:06:39 +1000	[thread overview]
Message-ID: <CANV1gkf+m1n3bLdBg3vP3pzSxiQ1Na53TSbUvLrNNqmKVZvgQQ@mail.gmail.com> (raw)
In-Reply-To: <20230522093208.NtKNYiYn@linutronix.de>

Yes, I won't be using a DKMS driver and will test with the in-tree driver.
I rolled a PC back to the Debian 6.1 RT kernel and the default in-tree
R8169 driver yesterday with isolcpus=2,3.

I had a shot at it last night with the napi thread but was confused by
the trace results so will try again.
I could not see our PacketErrorTest script appearing in the trace but
it stopped the trace when it should.
Also our RT process did not appear to be on an isolated thread which
seemed odd. I did not get as far as setting the affinity for napi.

I've also installed  Bookworm RC3 on another PC with the default RT
kernel on a Gigabyte Brix N3160 with an R8111/R8168 NIC and the
in-tree R8169 driver.
This PC historically had max latency of about 130000 ns  back with
kernel 4.x and now its reporting 23000 ns with the 6.1 kernel over 24
hours testing with the linuxcnc tools. Quite amazing what you guys
have achieved! It will be a few days before I can lug my hardware to
work to test on it as well for another data point.

I really appreciate your willingness to help. This remains a
frustrating issue for many Linuxcnc users who are using my compiled
6.3 kernel to get out of jail.
Bear with me as I bumble my way through!

Rod Webster





Rod Webster

VMN®

www.vmn.com.au

Ph: 1300 896 832

Mob: +61 435 765 611




On Mon, 22 May 2023 at 19:32, Sebastian Andrzej Siewior
<bigeasy@linutronix.de> wrote:
>
> On 2023-05-19 21:41:30 [+1000], Rod Webster wrote:
> > I will do some testing tomorrow now I know what's going on but I
> > wonder how relevant it will be given this turnaround?
>
> I'm not going to look at the dkms/OOT driver. If there is an actual
> problem or something odd with mainline and RT and I will look into it.
> I managed to find an older box which is using the r8169 and I'm going to
> boot and see if there the driver is doing something odd what I didn't
> see earlier…
>
> Please make sure that you are using the in-tree driver. If you
> experience high latencies then I'm willing to help investigate.
>
> > Rod Webster
>
> Sebastian

  reply	other threads:[~2023-05-22 10:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18  3:23 Excessive network latency when using Realtek R8168/R8111 et al NIC Rod Webster
2023-04-28  8:51 ` 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 [this message]
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=CANV1gkf+m1n3bLdBg3vP3pzSxiQ1Na53TSbUvLrNNqmKVZvgQQ@mail.gmail.com \
    --to=rod@vmn.com.au \
    --cc=bigeasy@linutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    /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).