CoDel AQM discussions
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Rodrigo Alvarez Dominguez <rodroleon@gmail.com>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] Codel configuration
Date: Mon, 14 Jan 2019 17:24:26 +0200	[thread overview]
Message-ID: <4D6E822B-A866-4513-90CF-93C6E6308F41@gmail.com> (raw)
In-Reply-To: <CALFXYB+VFQz9kH4zQdEcjGRn6XfeXkxpMJfACDUkkS4-Dk5EhA@mail.gmail.com>

> On 14 Jan, 2019, at 12:54 pm, Rodrigo Alvarez Dominguez <rodroleon@gmail.com> wrote:
> 
> I would like to know if it is possible to have the following configuration where there is a rate limit and codel algorithm configured over the same interface
>  
> tc qdisc add dev r1-eth0 root handle 1: htb
> tc class add dev r1-eth0 parent 1: classid 1:1 htb rate 10000kbit burst 15kbit
> tc qdisc add dev r1-eth0 parent 1:1 handle 10: fq_codel limit 1000 target 5000 interval 10000 noecn
> tc filter add dev r1-eth0 protocol ip prio 1 u32 match ip dst 0.0.0.0/0 flowid 1:1

Yes, this is an extensively tested configuration.  Have you tried it?

You could also just use Cake, which does all the above, better, with only one tc invocation:

	tc qdisc replace dev r1-eth0 root handle 1: cake bandwidth 10000kbit besteffort flows

 - Jonathan Morton


  reply	other threads:[~2019-01-14 15:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-14 10:54 Rodrigo Alvarez Dominguez
2019-01-14 15:24 ` Jonathan Morton [this message]
2019-01-14 16:17   ` Rodrigo Alvarez Dominguez
2019-01-14 16:48     ` Jonathan Morton
2019-01-14 22:10       ` Rodrigo Alvarez Dominguez
2019-01-15  1:14         ` Jonathan Morton
2019-01-15  9:27           ` Rodrigo Alvarez Dominguez
2019-01-15 16:48             ` Jonathan Morton
  -- strict thread matches above, loose matches on Subject: below --
2019-01-14 10:45 Rodrigo Alvarez Dominguez

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/codel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D6E822B-A866-4513-90CF-93C6E6308F41@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=codel@lists.bufferbloat.net \
    --cc=rodroleon@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