From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>
Cc: Georgios Amanakis <gamanakis@gmail.com>,
Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Fwd: Does the latest cake support "tc filter"?
Date: Wed, 30 May 2018 22:50:15 +0200 [thread overview]
Message-ID: <87efhsc1h4.fsf@toke.dk> (raw)
In-Reply-To: <CAA93jw7zay15H_72YgW0DOb7gjrts1JL229ba=m+9mbGmXMLrg@mail.gmail.com>
Dave Taht <dave.taht@gmail.com> writes:
> I also worry that the new tc filter related code is going to cause
> weirdness from other subsystems and deployments. Someone (for example)
> sets iptables priorities or something else for some other reason to
> make a set of iptables rules work (the skb-priority field is so
> massively overloaded), and that messes up what cake wants.
>
> this is why I elided tc filters entirely all those years ago. I guess
> the MAJ approach toke took is sufficient.
Yeah. Stole that from fq_codel, actually. That allows you to select a
queue using the priority field as well as with an explicit classifier
(with the same major number check). So guess that is relatively safe :)
-Toke
next prev parent reply other threads:[~2018-05-30 20:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 2:36 [Cake] " Fushan Wen
2018-05-17 10:42 ` Toke Høiland-Jørgensen
2018-05-30 19:14 ` Georgios Amanakis
2018-05-30 19:58 ` Toke Høiland-Jørgensen
[not found] ` <CACvFP_gbwHzR6Qk1fQFbgWm5TmMu1eEjV0bcj1FGfS9smn6dEw@mail.gmail.com>
2018-05-30 20:14 ` [Cake] Fwd: " Georgios Amanakis
2018-05-30 20:18 ` Dave Taht
2018-05-30 20:30 ` Toke Høiland-Jørgensen
2018-05-30 20:42 ` Dave Taht
2018-05-30 20:44 ` Georgios Amanakis
2018-05-30 20:51 ` Toke Høiland-Jørgensen
2018-05-30 20:46 ` Dave Taht
2018-05-30 20:50 ` Toke Høiland-Jørgensen [this message]
2018-05-30 20:47 ` Toke Høiland-Jørgensen
2018-05-30 20:31 ` [Cake] " Toke Høiland-Jørgensen
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
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efhsc1h4.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=gamanakis@gmail.com \
/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