netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "Thorsten Glaser" <t.glaser@tarent.de>,
	netdev@vger.kernel.org, Haye.Haehne@telekom.de,
	"Toke Høiland-Jørgensen" <toke@toke.dk>
Subject: Re: knob to disable locally-originating qdisc optimisation?
Date: Thu, 27 Apr 2023 16:37:15 -0700	[thread overview]
Message-ID: <20230427163715.285e709f@hermes.local> (raw)
In-Reply-To: <20230427132126.48b0ed6a@kernel.org>

On Thu, 27 Apr 2023 13:21:26 -0700
Jakub Kicinski <kuba@kernel.org> wrote:

> On Wed, 26 Apr 2023 14:54:30 +0200 (CEST) Thorsten Glaser wrote:
> > when traffic (e.g. iperf) is originating locally (as opposed to
> > forward traffic), the Linux kernel seems to apply some optimisations
> > probably to reduce overall bufferbloat: when the qdisc is “full” or
> > (and especially) when its dequeue often returns NULL (because packets
> > are delayed), the sender traffic rate is reduced by as much as ⅓ with
> > 40 ms extra latency (30 → 20 Mbit/s).  
> 
> Doesn't ring a bell, what's your setup?
> 
> > This is probably good in general but not so good for L4S where we
> > actually want the packets to queue up in the qdisc so they get ECN
> > marking appropriately (I guess there probably are some socket ioctls
> > or something with which the sending application could detect this
> > state; if so, we’d be interested in knowing about them as well).
> > 
> > This is especially bad in a testbed for writing L4S-aware applications,
> > so if there’s a knob (sysctl or something) to disable this optimisation
> > please do tell (I guess probably not, but asking doesn’t hurt).  

It might be BQL trying to limit outstanding packets locally.

  reply	other threads:[~2023-04-27 23:37 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 [this message]
2023-05-16 16:38     ` Thorsten Glaser
2023-05-16 19:23       ` Toke Høiland-Jørgensen
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=20230427163715.285e709f@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=Haye.Haehne@telekom.de \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=t.glaser@tarent.de \
    --cc=toke@toke.dk \
    /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).