General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Maximilian Bachl via Bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] The NetEm qdisc does not work in conjunction with other qdiscs
Date: Fri, 25 Oct 2024 14:02:30 -0700	[thread overview]
Message-ID: <20241025140230.5b1263b8@hermes.local> (raw)
In-Reply-To: <CAEXAmbvRkQMVEGQLWuqUeRTLe4+RQQHYSCQGZv=wKy7fkSsOuA@mail.gmail.com>

On Fri, 25 Oct 2024 21:55:21 +0200
Maximilian Bachl via Bloat <bloat@lists.bufferbloat.net> wrote:

> From my experience (experimented with it last year), it still behaves
> weirdly. You can use htb for the shaping and you can create delay using
> netem by using it on another (virtual) host on a link that does not have
> any other qdiscs and where the link is not the bottleneck.
> 
> Best regards,
> Max

Yes, netem has expectations about how inner qdisc behaves,
and other qdisc used as inner have expectations about how/when packets
are sent. There is a mismatch, not sure if it is fixable with in the
architecture of how Linux queue disciplines operate.

The best way is to use netem on an intermediate hop and not expect
it to work perfectly when used on an endpoint. The same is true of Dummynet
and other network emulators; they are uses as man-in-the-middle systems.


  reply	other threads:[~2024-10-25 21:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 12:24 [Bloat] Testbed using containers O. P.
2024-10-25 18:54 ` [Bloat] The NetEm qdisc does not work in conjunction with other qdiscs Joerg Deutschmann
2024-10-25 19:41   ` Dave Taht
2024-10-25 22:33     ` Joerg Deutschmann
2024-10-25 19:55   ` Maximilian Bachl
2024-10-25 21:02     ` Stephen Hemminger [this message]
2024-10-25 22:47       ` Joerg Deutschmann
2024-10-25 23:12         ` Dave Taht

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

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241025140230.5b1263b8@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=bloat@lists.bufferbloat.net \
    /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