lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <5aea96db-9248-6cff-d985-d4cd91a429@tarent.de> Date: Fri, 26 Aug 2022 21:34:47 +0200 (CEST) From: Thorsten Glaser <t.glaser@...ent.de> To: netdev@...r.kernel.org Subject: inter-qdisc communication? Hi, is it possible for qdiscs to communicate with each other? For example, if I have a normal egress qdisc and an ingress qdisc, how could I “share” configuration values so that e.g. a “tc change” can affect both in one run? Use case: we have a normal egress qdisc that does a lot of things. Now we add artificial latency, and we need to do that on ingress as well, for symmetry, obviously, so I’ll write a small qdisc that does just that for ingress. But we’re already firing a “tc change” to the egress qdisc every few ms or so, and I don’t want to double that overhead. 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! ****************************************************
Powered by blists - more mailing lists