From: Dave Taht <dave.taht@gmail.com>
To: ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: [Ecn-sane] rtt-fairness question
Date: Fri, 8 Apr 2022 09:33:57 -0700 [thread overview]
Message-ID: <CAA93jw4iMh8j=vcu2oPr2Of5=NdnwyosxfnifJtDEkHNz+Dixg@mail.gmail.com> (raw)
I have managed to drop most of my state regarding the state of various
dctcp-like solutions. At one level it's good to have not been keeping
up, washing my brain clean, as it were. For some reason or another I
went back to the original paper last week, and have been pounding
through this one again:
Analysis of DCTCP: Stability, Convergence, and Fairness
"Instead, we propose subtracting α/2 from the window size for each marked ACK,
resulting in the following simple window update equation:
One result of which I was most proud recently was of demonstrating
perfect rtt fairness in a range of 20ms to 260ms with fq_codel
https://forum.mikrotik.com/viewtopic.php?t=179307 )- and I'm pretty
interested in 2-260ms, but haven't got around to it.
Now, one early result from the sce vs l4s testing I recall was severe
latecomer convergence problems - something like 40s to come into flow
balance - but I can't remember what presentation, paper, or rtt that
was from. ?
Another one has been various claims towards some level of rtt
unfairness being ok, but not the actual ratio, nor (going up to the
paper's proposal above) whether that method had been tried.
My opinion has long been that any form of marking should look more
closely at the observed RTT than any fixed rate reduction method, and
compensate the paced rate to suit. But that's presently just reduced
to an opinion, not having kept up with progress on prague, dctcp-sce,
or bbrv2. As one example of ignorance, are 2 packets still paced back
to back? DRR++ + early marking seems to lead to one packet being
consistently unmarked and the other marked.
--
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
Dave Täht CEO, TekLibre, LLC
next reply other threads:[~2022-04-08 16:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 16:33 Dave Taht [this message]
2022-04-08 18:03 ` Michael Welzl
2022-04-12 15:51 ` David P. Reed
2022-04-12 16:00 ` Michael Welzl
2022-04-12 18:52 ` Sebastian Moeller
2022-04-12 19:07 ` Michael Welzl
2022-04-14 16:54 ` David P. Reed
2022-04-14 17:08 ` Dave Taht
2022-04-14 17:16 ` Dave Taht
2022-04-14 20:49 ` David P. Reed
2022-04-14 21:25 ` Sebastian Moeller
2022-04-19 20:40 ` David P. Reed
2022-04-19 21:36 ` Vint Cerf
2022-04-19 23:55 ` Rodney W. Grimes
2022-04-20 12:54 ` Sebastian Moeller
2022-04-20 22:21 ` David P. Reed
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='CAA93jw4iMh8j=vcu2oPr2Of5=NdnwyosxfnifJtDEkHNz+Dixg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=ecn-sane@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