Thread (1 message) 1 message, 1 author, 2022-08-29

Re: inter-qdisc communication?

From: Thorsten Glaser <hidden>
Date: 2022-08-29 16:13:40

On Mon, 29 Aug 2022, Dave Taht wrote:
had means to do this, so did my debloat script.
OK, this basically does the same but with protocol all.

I don’t need ready-made scripts, I need building blocks
and some amount of understanding.
quoted
(I could just use netem but there’s still the issue of inter-
qdisc communication which I’d *very* much like to have, not just
This is still open… nothing? No inter-module communication possible?

Ideally, I’d configure one of the qdiscs to know the handle and device¹
of another, and then its .change op would call the .change op (or a
special function) from the other, but I lack sufficient Linux kernel
experience (even locking for SMP is something I always fear to miss).

① it really would help if just the handle is enough; they are practically
  global (in my setup) anyway because they determine the debugfs filename

Alternatively, the ability to run multiple tc commands without having to
do multiple fork/exec of the binary would help. Maybe even a “continuous”
mode, in which the binary would REPL commands from stdin, running them as
they’re read…

Thanks in advance,
//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!
                        ****************************************************
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help