From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
"codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: [Codel] Fwd: [Ns-developers] GSOC 2014 Bufferbloat Weekly Report
Date: Tue, 15 Jul 2014 13:17:19 -0700 [thread overview]
Message-ID: <CAA93jw6gW1xDuPgGwn=yn4ke9hK_5FG6ARpXdaac1W8z0yhQwg@mail.gmail.com> (raw)
The google summer of code ns3 work on codel and fq_codel is starting
to bear fruit. In particular Anh has been working on the "classic"
bufferbloat model - one stream up, one stream down, one set of
isochronous flows, on an asymmetric network, (example, 20mbit down, 5
up).
Also, the codel module is in pretty good shape and it looks like
that can be upstreamed to the ns3 mainline code soon.
On the fq_codel front, we are running behind on removing the boost
dependencies, and dealing with ECN and tos bits, and getting
perilously close to some deadlines that might result in fq_codel not
making it into the next ns3 release.
The WIP hg (mercurial) repository is on [2] below.
Comments, feedback and requests appreciated.
---------- Forwarded message ----------
From: Anh Nguyen <annguyen@ittc.ku.edu>
Date: Mon, Jul 14, 2014 at 3:35 AM
Subject: [Ns-developers] GSOC 2014 Bufferbloat Weekly Report
To: ns-developers@isi.edu
Hi All,
Here are what I worked on last week
- Completed a test script to compare CoDel with Droptail, which supports
multiple up/down streams, asymmetric links, and isochronous.
- Modified CoDel to use Queue:QueueMode
My plan for this week includes:
-Add additional trace sources for CoDel: trace drop event and number of
drops during each event
-Add additional unit tests for CoDel to verify CoDel algorithm
More information about the project is available at [1]. The code can be
cloned from [2].
Best,
Anh
[1] http://www.nsnam.org/wiki/GSOC2014Bufferbloat
[2] http://code.nsnam.org/annguyen/ns-3-dev-aqm/summary
--
----------------------------------------------------------------------------
*Truc Anh N. Nguyen*
annguyen@ittc.ku.edu http://www.ittc.ku.edu/~annguyen
<http://www.ittc.ku.edu/~annguyen>
Information & Telecommunication Technology Center
Department of Electrical Engineering and Computer Science
The University of Kansas, Lawrence, KS 66045, USA
--
Dave Täht
NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
reply other threads:[~2014-07-15 20:17 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='CAA93jw6gW1xDuPgGwn=yn4ke9hK_5FG6ARpXdaac1W8z0yhQwg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--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