General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Joerg Deutschmann <joerg.deutschmann@fau.de>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] The NetEm qdisc does not work in conjunction with other qdiscs
Date: Fri, 25 Oct 2024 20:54:31 +0200	[thread overview]
Message-ID: <98eeb4b3-a8f8-4875-b021-aab0d5336959@fau.de> (raw)
In-Reply-To: <CANCLKUz4Evx-dd3kQ-p46brxU9j7gP_LQ0U39hrB1reZiAktEw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1521 bytes --]

Dear all,

bringing up again the question from a previous message to this list...

https://www.bufferbloat.net/projects/codel/wiki/Best_practices_for_benchmarking_Codel_and_FQ_Codel/#the-netem-qdisc-does-not-work-in-conjunction-with-other-qdiscs
says to not use NetEm together with other qdiscs.

Is this still true?

How could one emulate bottlenecks together with fq_codel?

Best regards
Joerg


On 15.01.24 13:24, O. P. via Bloat wrote:
> 
> Hi there,
> 
> I'm trying to set up a testbed to evaluate different AQM techniques 
> using docker containers.
> My first idea to create congestion was to use netem. However I later 
> came across 
> https://www.bufferbloat.net/projects/codel/wiki/Best_practices_for_benchmarking_Codel_and_FQ_Codel/ <https://www.bufferbloat.net/projects/codel/wiki/Best_practices_for_benchmarking_Codel_and_FQ_Codel/> which discourages using netem. Since the document is from 2014 and also states that "netem has been improving", my question was wether the current netem has improved sufficiently to be used to get realistic results.
> If netem has improved sufficienly, what would be the correct way to use 
> netem along fq, fq-codel or codel for example ?
> If not, is HTB still the best way to perform rate limiting ? Is there a 
> prefered way to combine HTB with AQMs ?
> 
> Best regards
> 
> John
> 
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4843 bytes --]

  reply	other threads:[~2024-10-25 18:54 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 ` Joerg Deutschmann [this message]
2024-10-25 19:41   ` [Bloat] The NetEm qdisc does not work in conjunction with other qdiscs Dave Taht
2024-10-25 22:33     ` Joerg Deutschmann
2024-10-25 19:55   ` Maximilian Bachl
2024-10-25 21:02     ` Stephen Hemminger
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=98eeb4b3-a8f8-4875-b021-aab0d5336959@fau.de \
    --to=joerg.deutschmann@fau.de \
    --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