From: Dave Taht <dave.taht@gmail.com>
To: Hagen Paul Pfeifer <hagen@jauu.net>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Programming assignment #1 in cs244 in Stanford
Date: Tue, 15 Jan 2013 20:12:43 -0500 [thread overview]
Message-ID: <CAA93jw5g4qXUuyHqybu+88Rw-QHnWOJAx4bEuzgvHmfqUZs3bw@mail.gmail.com> (raw)
In-Reply-To: <kvvw6bkhney7wyd5i3jl40b9.1358297839222@email.android.com>
On Tue, Jan 15, 2013 at 8:04 PM, Hagen Paul Pfeifer <hagen@jauu.net> wrote:
>> http://www.stanford.edu/class/cs244/2013/pa1.html
>
> The surprise for me is there network emulation component called mininet. Simple based on Linux network namespaces and some glue components, managed by a python script.
>
> I often dreamed of such a lightweight network virtualization framework! Powerful enough to replace my KVM-qemu, vde, ... setup - nice work!
My kvetch is that they are using a 100 buffers, (come on, use 1000,
FEEL the bloat)
... and the second part of the experiment uses 20 buffers, and I doubt
that the structure of it will show the side-effects what such a size
can cause in things such as tcp admission control. Perhaps that's
handled in a later module.
Either way it looks like a nice class, and a quick glance over mininet
makes me want to run screaming from ns2 as fast as possible in it's
general direction.
>
> Hagen
>
> --
> http://protocollabs.com
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2013-01-16 1:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 1:04 Hagen Paul Pfeifer
2013-01-16 1:12 ` Dave Taht [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-15 20:09 Dave Taht
2013-01-15 20:32 ` Roger Jørgensen
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw5g4qXUuyHqybu+88Rw-QHnWOJAx4bEuzgvHmfqUZs3bw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=hagen@jauu.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