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 18:06:41 -0700 [thread overview]
Message-ID: <20220826180641.1e856c1d@kernel.org> (raw)
In-Reply-To: <49bb3aa4-a6d0-7f38-19eb-37f270443e7e@tarent.de>
On Sat, 27 Aug 2022 02:45:02 +0200 (CEST) Thorsten Glaser wrote:
> > How do you add latency on ingress? 🤔
> > The ingress qdisc is just a stub to hook classifiers/actions.
>
> Oh, damn. Then, I guess, I’ll have to do that on egress on
> the other interface, which makes it at least symmetric for
> passing traffic but catch not the set of traffic it should.
> Especially not the traffic terminating locally. Meh.
>
> The question remains the same, just the use case magically
> mutated under me.
>
> (Maybe if there were documentation like an intro to qdisc
> writing like I asked for already, I’d have known that.)
These days the recommendation for adding workload specific sauce
at the qdisc layer is to use the fq qdisc (mq + fq if you have
a multi queue device) and add a BPF program on top (cls-bpf)
which sets transmission times for each packet.
Obviously you can still write a qdisc if you wish or your needs
are sufficiently hardcore.
On the docs, nothing official AFAIK, if it doesn't pop up in
the first two pages of Google results it probably doesn't exist :(
next prev parent reply other threads:[~2022-08-27 1: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
2022-08-27 0:45 ` Thorsten Glaser
2022-08-27 1:06 ` Jakub Kicinski [this message]
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=20220826180641.1e856c1d@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