From: Joerg Deutschmann <joerg.deutschmann@fau.de>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] The NetEm qdisc does not work in conjunction with other qdiscs
Date: Sat, 26 Oct 2024 00:33:35 +0200 [thread overview]
Message-ID: <4e24ef69-9ddc-4eb3-8c4b-8970a5ebe590@fau.de> (raw)
In-Reply-To: <CAA93jw7_PoRHEHVoT66d990m7dOvyFPAM=V3i-Bdz8CB5Xq0SQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 708 bytes --]
> What I would typically do is setup netem on an inbound qdisc and
> whatever is under test on the outbound.
Thanks, this is good advice.
> even then, care is needed to ensure netem itself is not the bottleneck,
> has an appropriate packet limit (I use millions), and that you are not
> running out of cpu. For example it is really hard to pull 4gbit on cheap
> hw with default qdiscs.
👍
As I'm not an expert regarding qdiscs, this command line example was
useful showing how to configure an ingress qdisc:
https://serverfault.com/questions/984822/how-to-remove-the-ingress-delay-introduced-using-tc
(Note that it does not set a higher packet limit as you correctly
recommended.)
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4843 bytes --]
next prev parent reply other threads:[~2024-10-25 22:33 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 [this message]
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=4e24ef69-9ddc-4eb3-8c4b-8970a5ebe590@fau.de \
--to=joerg.deutschmann@fau.de \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.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