From: "Igor Maravić" <igorm@etf.rs>
To: Dave Taht <dave.taht@gmail.com>
Cc: codel@lists.bufferbloat.net,
bloat-devel <bloat-devel@lists.bufferbloat.net>,
aqm@ietf.org
Subject: Re: [Codel] [Ns-developers] NS-3 has been accepted for GSOC 2013
Date: Tue, 16 Apr 2013 11:01:13 +0200 [thread overview]
Message-ID: <CAFdo_mX2i+_FMH5FmOY1B79irGnWFYr4f7u+ixfFDUEmaqOrMg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7P1tR=ustWfEhp7OMgDUZU4O49=DCZJUmPydyzifsJvQ@mail.gmail.com>
Hi Dave,
I did some work in ns-3 related to the bufferbloat.
I've fixed some things inside CoDel, implemented ECN support for TCP,
DCTCP, D2TCP, Adaptive RED, FIFO FAST, GRED and ECN inside CoDel.
If you, or anyone else, is interested, I've put this code on my GitHub:
https://github.com/i-maravic/ns-3
I currently don't have the time to polish this up for the ns-3
upstreaming process.
BR
Igor
2013/4/9 Dave Taht <dave.taht@gmail.com>:
> Andrew and I haven't had time to update the ns3 model to the current
> versions of codel, fq_codel, and sfq_codel. I don't really expect that time
> to materialize.
>
> However I am certainly willing to mentor someone (other mentors would be
> good, too!) on moving the codebase forward (and developing further
> tests/papers) and pushing it into the mainline code, this summer, as part of
> the GSOC program.
>
> https://www.nsnam.org/wiki/index.php/GSOC2013Projects#INSTOOLS_for_ns-3
>
> Any takers? See further below for more details.
>
> The old (may, 2012) ns3 codebase is in git
>
> https://github.com/dtaht/ns-3-dev
>
> and the latest ns2 codebase which has sfq_codel in it is hosted on pollere
>
> http://pollere.net/CoDel.html
>
> Despite the name the sfq_codel codebase has morphed to be very similar to
> the fq_codel codebase, but they do remain different in several approaches.
>
> ---------- Forwarded message ----------
> From: Lalith Suresh <suresh.lalith@gmail.com>
> Date: Mon, Apr 8, 2013 at 12:01 PM
> Subject: [Ns-developers] NS-3 has been accepted for GSOC 2013
> To: ns-developers <ns-developers@isi.edu>
>
>
> Hi everyone,
>
> I'm very pleased to inform you that ns-3 has been accepted for Google
> Summer of Code 2013. Thanks to everyone who helped prepare our ideas
> page [1]!
>
> Students are encouraged to go through our Ideas list and begin
> discussing their plans on the ns-developers mailing list to get
> feedback from the developers. Also, start preparing your applications
> as per our template [2]. The earlier you begin, the more refined your
> application will be, so start now! You will soon be able to find ns-3
> on Melange [3] after which you can begin filling in your application
> there.
>
> Please note: there is a simple test this year for all student
> applicants. Please refer to [4] for details.
>
>
> [1] https://www.nsnam.org/wiki/index.php/GSOC2013Projects
> [2] https://www.nsnam.org/wiki/index.php/GSOC2013StudentApplicationTemplate
> [3] http://www.google-melange.com/gsoc/homepage/google/gsoc2013
> [4] https://www.nsnam.org/wiki/index.php/GSOC2013PatchRequirement
>
>
> --
> Lalith Suresh
> www.lalith.in
>
>
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt:
> http://www.teklibre.com/cerowrt/subscribe.html
> _______________________________________________
> Bloat-devel mailing list
> Bloat-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat-devel
>
prev parent reply other threads:[~2013-04-16 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOj7qWbJKzbootw2G0L9Br=hMXCF1a5E9DPbsDboy5gC=Jupug@mail.gmail.com>
2013-04-09 8:17 ` [Codel] Fwd: " Dave Taht
2013-04-16 9:01 ` Igor Maravić [this message]
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=CAFdo_mX2i+_FMH5FmOY1B79irGnWFYr4f7u+ixfFDUEmaqOrMg@mail.gmail.com \
--to=igorm@etf.rs \
--cc=aqm@ietf.org \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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