From: Rodrigo Alvarez Dominguez <rodroleon@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] Codel configuration
Date: Mon, 14 Jan 2019 17:17:44 +0100 [thread overview]
Message-ID: <CALFXYB+X2VAJ=5JdjNjuZLrNcoXsaSWOdGcZ98=gmfXokAnHdw@mail.gmail.com> (raw)
In-Reply-To: <4D6E822B-A866-4513-90CF-93C6E6308F41@gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1926 bytes --]
Hi Jonathan
Thanks for your quick answer. REally appreciate it!!!
I wil try later the cake statement (is it the same as codel)?. I am
starting with Codel. So I need to have a better understanding of codel.
I have the following scenario
[image: image.png]
Where client asks for a FTP file to server. Link between router-server has
a 150MBit speed with a delay of 250 ms.
Then link between client and router has 10 Mbit and the Codel algorithm. So
I am checking the differences between having codel or not.
*Do you have an advice to have a good scenario for testing Codel properly?
Or a document to know how the differences parameter can affect to the
communication?*
In my scenario it seems it is better not having Codel. See attached
ClientFTPCodelNO-NO-NO (nocodel) versus ClientFtpCodel1000..
where a Codel Algorithm of 1000 packets, 13 ms target and 100 interval is
configured
Regards.
El lun., 14 ene. 2019 a las 16:24, Jonathan Morton (<chromatix99@gmail.com>)
escribió:
> > 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
>
>
[-- Attachment #1.1.2: Type: text/html, Size: 2540 bytes --]
[-- Attachment #1.2: image.png --]
[-- Type: image/png, Size: 18472 bytes --]
[-- Attachment #2: client-FTPfqcodelNO-NO-NO-file_70MB-10000-250-150000-250.pdf --]
[-- Type: application/pdf, Size: 16281 bytes --]
[-- Attachment #3: client-FTPfqcodel1000-13000-100000-file_70MB-10000-250-150000-250.pdf --]
[-- Type: application/pdf, Size: 17179 bytes --]
next prev parent reply other threads:[~2019-01-14 16:17 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 [this message]
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='CALFXYB+X2VAJ=5JdjNjuZLrNcoXsaSWOdGcZ98=gmfXokAnHdw@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