From: Dave Taht <dave.taht@gmail.com>
To: ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: [Ecn-sane] some l4s and sce gsoc work items planned for ns3
Date: Sat, 16 May 2020 11:16:54 -0700 [thread overview]
Message-ID: <CAA93jw4s-pqV4PH1zoAF61xP2OGS-B=7KwOpvZp2eYbaCAbZwg@mail.gmail.com> (raw)
In-Reply-To: <CAC2TnRwUWVXOuORe79BSk4edNNyyC+4GNOAtUJ16hFYS-0OMCQ@mail.gmail.com>
forwarding this on behalf of tom who is having trouble with his mailer lately.
---------- Forwarded message ---------
From: Tom Henderson <tomhend@uw.edu>
Date: Fri, May 15, 2020 at 11:38 AM
Subject: Resending: Re: tcp prague bug in ns3 also?
To: <dave.taht@gmail.com>
Dave and all,
I discovered a few minutes ago that my outbound email to Gmail.com
addresses has started to experience some delivery issues this morning,
so you may not have received the below, which I'm now resending.
Dave, I see you just ask ecn-sane; I can try to follow up there as well.
- Tom
On 5/14/20 11:20 PM, Dave Taht wrote:
do you know if tcp prague bug found (no response to loss in the ll
queue) recently in the linux version... is in the ns3 version?
and where's the current branch?
Hi Dave,
It should not be susceptible to that; it is a completely different
implementation than the Linux Prague.
Current version has been dormant for a few months and is here:
https://gitlab.com/JoakimMisund/l4s-evaluation/tree/tcp-prague
Current status is different from that of Linux. ns-3 version is DCTCP
plus the 'paced chirping' startup that Joakim Misund added. ns-3
version does not have RTT independence, 3168 detection/fallback, or
pacing alignments with Linux for congestion avoidance phase.
We have a GSoC student (Deepak K, cc'ed in this response) who plans to
align the ns-3 model with the Linux code, adding the missing features.
That project is about to start.
We also have another GSoC project that is currently planned to add SCE
TCP extensions and SCE-based AQMs, although we are waiting to see what
tsvwg decides (if anything) this month.
If you or anyone else is interested in tracking these projects, here
are the initial wiki pages:
https://www.nsnam.org/wiki/GSOC2020Prague
https://www.nsnam.org/wiki/GSOC2020AQM
and we are setting up public chat threads for each project on this
Zulip channel:
https://ns-3.zulipchat.com
- Tom
--
"For a successful technology, reality must take precedence over public
relations, for Mother Nature cannot be fooled" - Richard Feynman
dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
parent reply other threads:[~2020-05-16 18:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAC2TnRwUWVXOuORe79BSk4edNNyyC+4GNOAtUJ16hFYS-0OMCQ@mail.gmail.com>]
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='CAA93jw4s-pqV4PH1zoAF61xP2OGS-B=7KwOpvZp2eYbaCAbZwg@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