netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Thorsten Glaser <t.glaser@tarent.de>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: Jakub Kicinski <kuba@kernel.org>,
	netdev@vger.kernel.org, Haye.Haehne@telekom.de
Subject: Re: knob to disable locally-originating qdisc optimisation?
Date: Tue, 16 May 2023 21:23:08 +0200	[thread overview]
Message-ID: <877ct8cc83.fsf@toke.dk> (raw)
In-Reply-To: <998e27d4-8a-2fd-7495-a8448a5427f9@tarent.de>

Thorsten Glaser <t.glaser@tarent.de> writes:

> On Thu, 27 Apr 2023, Stephen Hemminger wrote:
>
>>On Thu, 27 Apr 2023 13:21:26 -0700
>>Jakub Kicinski <kuba@kernel.org> wrote:
>
>>> Doesn't ring a bell, what's your setup?
>
> Intel NUC with Debian bullseye on it and a custom qdisc that
> limits and delays outgoing traffic, therefore occasionally
> returning NULL from .dequeue even if the qdisc is not empty.
>
> iperf3 sending from the same NUC to a device on the network
> behind that qdisc where the corresponding iperf server runs.
>
>>It might be BQL trying to limit outstanding packets locally.
>
> Possibly?

Sounds like it's TSQ kicking in? The objective of that is to provide the
maximum backpressure against the application socket buffer, precisely so
the application can better react to congestion. Turning that off isn't
going to help your E2E latency, quite the contrary. Pushing stuff into a
qdisc so it can be ECN-marked is also nonsensical for locally generated
traffic; you don't need the ECN roundtrip, you can just directly tell
the local TCP sender to slow down (which is exactly what TSQ does).

-Toke

  reply	other threads:[~2023-05-16 19:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26 12:54 knob to disable locally-originating qdisc optimisation? Thorsten Glaser
2023-04-27 20:21 ` Jakub Kicinski
2023-04-27 23:37   ` Stephen Hemminger
2023-05-16 16:38     ` Thorsten Glaser
2023-05-16 19:23       ` Toke Høiland-Jørgensen [this message]
2023-05-16 20:20         ` Thorsten Glaser
2023-05-16 22:11           ` Toke Høiland-Jørgensen
2023-05-16 23:01             ` Stephen Hemminger
2023-05-16 23:40               ` Thorsten Glaser
2023-05-16 23:44                 ` Stephen Hemminger
2023-05-16 23:47                   ` Thorsten Glaser
2023-05-17  3:02                     ` Stephen Hemminger
2023-05-17 15:53                       ` Thorsten Glaser
2023-05-16 23:41             ` Thorsten Glaser
2023-05-17 10:00               ` Toke Høiland-Jørgensen

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=877ct8cc83.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=Haye.Haehne@telekom.de \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    --cc=t.glaser@tarent.de \
    /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).