From: Georgios Amanakis <gamanakis@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"Cake List" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Fwd: Does the latest cake support "tc filter"?
Date: Wed, 30 May 2018 16:44:11 -0400 [thread overview]
Message-ID: <CACvFP_hL+-_jKT_b7KTTmkWRjG_k1EPQpPw6N_qJU7i30JQACA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6T3gaM=hvLu40q5XuDRWvOccxtSf6kzm66uwR9X4WoeQ@mail.gmail.com>
I don't have an explicit use case right now, but it gives somewhat
greater flexibility in classifying packets.
Particularly in the ingress mode with ifb (this would mostly apply to
an end-device, not so much to traffic being forwarded through a
router). We cannot set DSCP flags on incoming packets, since they just
arrived. However, we can use a filter on cake to assign them
explicitly to a tin.
We can do the following:
#tc qdisc add dev enp1s0 ingress handle ffff
#tc qdisc add dev ifb0 root handle 8002 cake bandwidth 11800kbit
diffserv3 ingress
#tc filter add dev ifb0 parent 8002: protocol ip \
u32 match ip src 1.2.3.4/32 \
action skbedit priority 8002:3
#tc filter add dev enp1s0 parent ffff: protocol all \
u32 match u32 0 0 \
action mirred egress redirect dev ifb0
George
next prev parent reply other threads:[~2018-05-30 20:44 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 [this message]
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
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=CACvFP_hL+-_jKT_b7KTTmkWRjG_k1EPQpPw6N_qJU7i30JQACA@mail.gmail.com \
--to=gamanakis@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=toke@toke.dk \
/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