From: Rodrigo Alvarez Dominguez <rodrigo.alvarez.dominguez@gmail.com>
To: codel@lists.bufferbloat.net
Subject: [Codel] Codel+netem
Date: Thu, 27 Dec 2018 11:14:07 +0100 [thread overview]
Message-ID: <CAGCY_Tz3=uqGDk0h8XSAObYYm=2nQL019VbDnsU16+CZNV3+qg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 582 bytes --]
Hi
I would like to test an environment where there is a ftp client + router +
ftp server.
The router will have a fqcodel in the interface
client-router link will have a netem delay + rate
router-server link will have a netem delay + rate
The router interface of the client-router link will have the fq codel
implementation of linux
I am not sure if it should work after reading this
https://www.bufferbloat.net/projects/codel/wiki/Best_practices_for_benchmarking_Codel_and_FQ_Codel/
It seems that FQ_Codel + netem is incompatible. Am I right?
Thanks in advance,
Regards,
Rodrigo
[-- Attachment #2: Type: text/html, Size: 900 bytes --]
reply other threads:[~2018-12-27 10:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAGCY_Tz3=uqGDk0h8XSAObYYm=2nQL019VbDnsU16+CZNV3+qg@mail.gmail.com' \
--to=rodrigo.alvarez.dominguez@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