From: Dave Taht <dave.taht@gmail.com>
To: ECN-Sane <ecn-sane@lists.bufferbloat.net>,
BBR Development <bbr-dev@googlegroups.com>,
flent-users <flent-users@flent.org>
Subject: [Ecn-sane] duplicating the BBRv2 tests at iccrg in flent?
Date: Fri, 5 Apr 2019 09:42:24 +0200 [thread overview]
Message-ID: <CAA93jw6F0QPzKE-M6H_WOQ1EfM+6L5XEL_a+uEMYdU+OByVUaQ@mail.gmail.com> (raw)
I see from the iccrg preso at 7 minutes 55 s in, that there is a test
described as:
20 BBRv2 flows
starting each 100ms, 1G, 1ms
Linux codel with ECN ce_threshold at 242us sojurn time.
I interpret this as
20 flows, starting 100ms apart
on a 1G link
with a 1ms transit time
and linux codel with ce_threshold 242us
0) This is iperf? There is no crypto?
1) "sojourn time" not as as setting the codel target to 242us?
I tend to mentally tie the concept of sojourn time to the target
variable, not ce_threshold
2) In our current SCE work we have repurposed ce_threshold to do sce
instead (to save on cpu and also to make it possible to fiddle without
making a userspace api change). Should we instead create a separate
sce_threshold option to allow for backward compatible usage?
3) Transit time on your typical 1G link is actually 13us for a big
packet, why 1ms?
is that 1ms from netem?
4) What is the topology here?
host -> qdisc -> wire -> host?
host -> qdisc -> wire -> router -> host?
5) What was the result with fq_codel instead?
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
next reply other threads:[~2019-04-05 7:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 7:42 Dave Taht [this message]
2019-04-05 15:10 ` [Ecn-sane] [bbr-dev] " Neal Cardwell
2019-04-05 15:51 ` Dave Taht
2019-04-05 16:58 ` Neal Cardwell
2019-04-05 16:20 ` Jonathan Morton
2019-04-06 11:56 ` Neal Cardwell
2019-04-06 14:37 ` [Ecn-sane] [Flent-users] " Sebastian Moeller
2019-04-09 1:33 ` Neal Cardwell
2019-04-09 2:09 ` Jonathan Morton
2019-04-09 6:30 ` Sebastian Moeller
2019-04-09 14:33 ` Neal Cardwell
2019-04-09 17:20 ` Sebastian Moeller
2019-04-06 11:49 ` [Ecn-sane] " Dave Taht
2019-04-06 12:31 ` Neal Cardwell
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/ecn-sane.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw6F0QPzKE-M6H_WOQ1EfM+6L5XEL_a+uEMYdU+OByVUaQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bbr-dev@googlegroups.com \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=flent-users@flent.org \
/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