From: Wei Bai <Wei.Bai@microsoft.com>
To: Dave Taht <dave.taht@gmail.com>,
ECN-Sane <ecn-sane@lists.bufferbloat.net>
Cc: "kaichen@cse.ust.hk" <kaichen@cse.ust.hk>,
Junxue ZHANG <jzhangcs@connect.ust.hk>
Subject: Re: [Ecn-sane] [EXTERNAL] comments: "Enabling ECN for Datacenter Networks with RTT Variations"
Date: Tue, 31 Dec 2019 01:56:37 +0000 [thread overview]
Message-ID: <HK0P153MB0145C7D6BA108E90746B3357FE260@HK0P153MB0145.APCP153.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAA93jw6cu_9cDrSfr=bvCvwqinUk_n9DVs=n9gUkERaHOA=grg@mail.gmail.com>
+Junxue
-----Original Message-----
From: Dave Taht <dave.taht@gmail.com>
Sent: Sunday, December 29, 2019 8:03 PM
To: ECN-Sane <ecn-sane@lists.bufferbloat.net>
Cc: kaichen@cse.ust.hk; Wei Bai <Wei.Bai@microsoft.com>
Subject: [EXTERNAL] comments: "Enabling ECN for Datacenter Networks with RTT Variations"
this ecn# & codel in p4 paper had probably of most interest to me four points:
1) Codel like algorithm on a tofino switch, implemented in p4
2) with some source code published... Not the p4 code, darn it...
unless I missed it?
but a detailed description of how they used the timestamp field was neat
3 Honestly I'd never thought about how much rtt variation a dc had,
nor do I know if this model is correct
3) Not really clear what parameters the used for codel
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fresource.hpisys.com%2Fseminar-papers%2F2019%2Fpaper%2F20191108_CoNEXT2019_Enabling%2520ECN%2520for%2520Datacenter%2520Networks%2520with%2520RTT%2520Variations.pdf&data=02%7C01%7CWei.Bai%40microsoft.com%7C72909f0aab234fe9d7a308d78cdd2d4e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637132754919827546&sdata=xQpBmCOlUsWEDKL3UA3y4wMlzDj3eQw1O5a7Tb0gIrk%3D&reserved=0
"Despite being successful, prior ECN-based transports have an
important drawback: they adopt a fxed RTT value in calculating
instantaneous ECN marking threshold while overlooking the RTT
variations in practice. In this paper, we reveal that the current
practice of using a fxed high-percentile RTT for ECN threshold
calculation can lead to persistent queue buildups, signifcantly
increasing packet latency. On the other hand, directly adopting lower
percentile RTTs results in throughput degradation. To handle the
problem, we introduce ECN!, a simple yet efective solution to enable
ECN for RTT variations. At its heart, ECN! inherits the current
instantaneous ECN marking (based on a high-percentile RTT) to achieve
high throughput and burst tolerance, while further marking packets
(conservatively) upon detecting long-term queue buildups to eliminate
unnecessary queueing delay without degrading throughput. We implement
ECN! on a Barefoot Tofno switch"
--
Make Music, Not War
Dave Täht
CTO, TekLibre, LLC
https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.teklibre.com&data=02%7C01%7CWei.Bai%40microsoft.com%7C72909f0aab234fe9d7a308d78cdd2d4e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637132754919827546&sdata=gB6EAR3riemq8XK02rsZYprZ0pnuUnk4RTNYDYQ%2FfM8%3D&reserved=0
Tel: 1-831-435-0729
next prev parent reply other threads:[~2019-12-31 1:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 4:02 [Ecn-sane] " Dave Taht
2019-12-31 1:56 ` Wei Bai [this message]
2020-01-04 22:01 ` Dave Taht
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=HK0P153MB0145C7D6BA108E90746B3357FE260@HK0P153MB0145.APCP153.PROD.OUTLOOK.COM \
--to=wei.bai@microsoft.com \
--cc=dave.taht@gmail.com \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=jzhangcs@connect.ust.hk \
--cc=kaichen@cse.ust.hk \
/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