From: Thorsten Glaser <t.glaser@tarent.de>
To: Dave Taht <dave.taht@gmail.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: inter-qdisc communication?
Date: Sat, 27 Aug 2022 04:00:02 +0200 (CEST) [thread overview]
Message-ID: <21f823b-aa56-95fc-6da7-85aeddba705c@tarent.de> (raw)
In-Reply-To: <CAA93jw66wYTAWQoAcEU-1=GxKe61U9_j__zMkooyODrLO=wnFQ@mail.gmail.com>
On Fri, 26 Aug 2022, Dave Taht wrote:
> This has some useful info on using netem properly, inc latency
> https://www.bufferbloat.net/projects/codel/wiki/Best_practices_for_benchmarking_Codel_and_FQ_Codel/
It mostly has that netem cannot be used together with other qdiscs,
and my colleague found that out, the hard way, as well. So I need to
implement that part myself as well. I have an idea for egress, but
nothing past that yet.
bye,
//mirabilos
--
Infrastrukturexperte • tarent solutions GmbH
Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/
Telephon +49 228 54881-393 • Fax: +49 228 54881-235
HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
****************************************************
/⁀\ The UTF-8 Ribbon
╲ ╱ Campaign against Mit dem tarent-Newsletter nichts mehr verpassen:
╳ HTML eMail! Also, https://www.tarent.de/newsletter
╱ ╲ header encryption!
****************************************************
next prev parent reply other threads:[~2022-08-27 2:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 19:34 inter-qdisc communication? Thorsten Glaser
2022-08-27 0:06 ` Jakub Kicinski
2022-08-27 0:45 ` Thorsten Glaser
2022-08-27 1:06 ` Jakub Kicinski
2022-08-27 1:16 ` Thorsten Glaser
[not found] ` <CAA93jw66wYTAWQoAcEU-1=GxKe61U9_j__zMkooyODrLO=wnFQ@mail.gmail.com>
2022-08-27 2:00 ` Thorsten Glaser [this message]
2022-08-29 15:03 ` Thorsten Glaser
2022-08-29 15:38 ` Thorsten Glaser
2022-08-29 16:18 ` Dave Taht
[not found] ` <CAA93jw5caRUDf1Xf+o0HV6Q1oNpTQzRKzYvCUzjXffHEf+h5Cg@mail.gmail.com>
2022-08-29 16:13 ` Thorsten Glaser
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=21f823b-aa56-95fc-6da7-85aeddba705c@tarent.de \
--to=t.glaser@tarent.de \
--cc=dave.taht@gmail.com \
--cc=netdev@vger.kernel.org \
/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