Netdev List
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Thorsten Glaser <t.glaser@tarent.de>
Cc: netdev@vger.kernel.org
Subject: Re: inter-qdisc communication?
Date: Fri, 26 Aug 2022 17:06:32 -0700	[thread overview]
Message-ID: <20220826170632.4c975f21@kernel.org> (raw)
In-Reply-To: <5aea96db-9248-6cff-d985-d4cd91a429@tarent.de>

On Fri, 26 Aug 2022 21:34:47 +0200 (CEST) Thorsten Glaser wrote:
> 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.

How do you add latency on ingress? 🤔 
The ingress qdisc is just a stub to hook classifiers/actions. 

  reply	other threads:[~2022-08-27  0:06 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 [this message]
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
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=20220826170632.4c975f21@kernel.org \
    --to=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=t.glaser@tarent.de \
    /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