Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Georgios Amanakis <gamanakis@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>,
	"Cake List" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Does the latest cake support "tc filter"?
Date: Wed, 30 May 2018 15:14:11 -0400	[thread overview]
Message-ID: <CACvFP_hiZoL7kP5esP_MLsZk7W_yjtc6kMko_WyF3-P9a5uEWQ@mail.gmail.com> (raw)
In-Reply-To: <87muwyy34k.fsf@toke.dk>

> Yes, the version submitted to upstream supports this. You can override
> which tin packets goes in by setting skb->priority from a filter or
> application (the major number needs to be set to the qdisc ID, and the
> minor number becomes the tin to queue packets in).

Toke could you give an example how to do this?

I am trying to put all traffic into tin 0:
#tc qdisc add dev enp1s0 root handle 8001 cake diffserv3 bandwidth 2mbit
#tc filter add dev enp1s0 parent 8001: protocol all \
              u32 match u32 0 0 \
              action skbedit priority 8001:1

However as soon as the second command is executed all traffic drops,
and it only resumes once I remove the filter.

What am I doing wrong?

Thank you,
George

On Thu, May 17, 2018 at 6:42 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Fushan Wen <qydwhotmail@gmail.com> writes:
>
>> Hello developers,
>> I've seen the mail in the netdev mailing list, saying "other tc
>> filters supported". So can I use "tc filter" to attach specified
>> traffic to a specified tin without DSCP marks? It's helpful when
>> dealing with ingress traffic where iptables DSCP mark won't work.
>
> Yes, the version submitted to upstream supports this. You can override
> which tin packets goes in by setting skb->priority from a filter or
> application (the major number needs to be set to the qdisc ID, and the
> minor number becomes the tin to queue packets in).
>
> However, these changes have not been backported, so they are not
> available in the cobalt branch. You can pull them from the upstream-4.18
> branch instead. That should build against a current net-next tree, and
> possibly a bit older. Alternatively, you can pull the current patches
> from patchwork and use those. Or wait for a backport after we're done
> with the upstream submission :)
>
> -Toke
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake

  reply	other threads:[~2018-05-30 19:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17  2:36 Fushan Wen
2018-05-17 10:42 ` Toke Høiland-Jørgensen
2018-05-30 19:14   ` Georgios Amanakis [this message]
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
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_hiZoL7kP5esP_MLsZk7W_yjtc6kMko_WyF3-P9a5uEWQ@mail.gmail.com \
    --to=gamanakis@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --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