General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Fwd: [Ns-developers] BitTorrent for ns-3: Call for Code Review
Date: Wed, 19 Dec 2012 07:09:58 -0500	[thread overview]
Message-ID: <CAA93jw7LYFbZYV2wh1NSXQCK0+qe+MJNWh5-xn3ZHGvv-DZ-7g@mail.gmail.com> (raw)
In-Reply-To: <50D19D6B.3000809@cs.rwth-aachen.de>

I would like very much to be able to analyze stuff like fq_codel under
bit torrent like loads.

So I'm happy to see this landing, and yet the codel/fq_codel sims in
ns3 need some love and also pushed into mainline ns3.


---------- Forwarded message ----------
From: Elias Weingärtner <elias.weingaertner@cs.rwth-aachen.de>
Date: Wed, Dec 19, 2012 at 5:56 AM
Subject: [Ns-developers] BitTorrent for ns-3: Call for Code Review
To: ns-developers@isi.edu, René Glebke <rene.glebke@rwth-aachen.de>,
Alexander Hocks <alexander.hocks@rwth-aachen.de>


Hi there,

on the last WNS3 workshop we presented a BitTorrent model for ns-3. We
now want to contribute this model to the official distribution ns-3
and ask for a code review. The model was jointly developed by René
Glebke, Alexander Hocks, Martin Lang and Elias Weingärtner.

The current distribution of our model is based on ns-3.15. It supports
emulation and comprises a BitTorrent tracker and a BitTorrent client
model.

The source code of model builds on Linux and Mac OS X. We have not
tested building it on Windows and other operating systems yet.



Obtaining the source code
=========================

1) Get the bundle at
https://www.comsys.rwth-aachen.de/fileadmin/downloads/projects/vodsim/vodsim.hg

2) Create a fresh repository using hg init

3) Import bundle using hg unbundle

4) hg update


Using the model
=========================

The model can either be used standalone or using a domain specific
language to set up a simulation scenario. A quick start guide how to
use everything is in src/bittorrent/examples

Input folder
=========================

Our model requires different kinds of input files:

- .torrent files
- Files in the payload
- Story files controlling the simulation.

In order not to clutter ns-3, we have introduced the new folder
"input" in the root of ns-3. We propose this folder to be hold input
files for all kinds of different models.


We look forward to your comments and hope that the model can become a
official part of ns-3 some time in spring next year.

best regards,

Elias Weingärtner



--
Dipl.-Inf. Elias Weingaertner
Research Assistant
Communication Systems Group
RWTH Aachen
Germany
http://www.comsys.rwth-aachen.de/team/elias-weingaertner/


-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

       reply	other threads:[~2012-12-19 12:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <50D19D6B.3000809@cs.rwth-aachen.de>
2012-12-19 12:09 ` Dave Taht [this message]
2012-12-19 12:25   ` Jesper Louis Andersen

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=CAA93jw7LYFbZYV2wh1NSXQCK0+qe+MJNWh5-xn3ZHGvv-DZ-7g@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@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