CoDel AQM discussions
 help / color / mirror / Atom feed
From: Rodrigo Alvarez Dominguez <rodroleon@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] Codel configuration
Date: Tue, 15 Jan 2019 10:27:33 +0100	[thread overview]
Message-ID: <CALFXYB+v3Uen4zT5pTPCJsH4hNVQFkUuHt9eZkR1q8j6C-mq5A@mail.gmail.com> (raw)
In-Reply-To: <DCEC80B6-10E5-47D4-8C6C-5CFD2ECFB48A@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 786 bytes --]

Hi
Is it cake working with UDP? I am going to test codel with QUIC QUIC is a
protocol that works using UDP protocol.
 At first test it seems cake is not limiting at 10000 kbit in a mininet
environment

     r1.cmd("tc qdisc replace dev r1-eth0 root handle 1: cake bandwidth
%skbit besteffort flows rtt 1800ms" %(dlrate))
Regards


El mar., 15 ene. 2019 a las 2:14, Jonathan Morton (<chromatix99@gmail.com>)
escribió:

> > On 15 Jan, 2019, at 12:10 am, Rodrigo Alvarez Dominguez <
> rodroleon@gmail.com> wrote:
> >
> > Is cake autotuning the target and interval?
>
> Yes.  It takes into account several parameters, including the configured
> 'rtt' (100ms is the default for that).  You can see what it chooses using
> 'tc -s qdisc'.
>
>  - Jonathan Morton
>
>

[-- Attachment #1.2: Type: text/html, Size: 1246 bytes --]

[-- Attachment #2: client-fqcodel1000-25000-250000-file_70MB-10000-250-150000-250.pdf --]
[-- Type: application/pdf, Size: 16277 bytes --]

  reply	other threads:[~2019-01-15  9:27 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
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 [this message]
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=CALFXYB+v3Uen4zT5pTPCJsH4hNVQFkUuHt9eZkR1q8j6C-mq5A@mail.gmail.com \
    --to=rodroleon@gmail.com \
    --cc=chromatix99@gmail.com \
    --cc=codel@lists.bufferbloat.net \
    /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