[Bloat] The NetEm qdisc does not work in conjunction with other qdiscs
Joerg Deutschmann
joerg.deutschmann at fau.de
Fri Oct 25 18:33:35 EDT 2024
> 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.)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4843 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://lists.bufferbloat.net/pipermail/bloat/attachments/20241026/8e0455ee/attachment.bin>
More information about the Bloat
mailing list