DCCP protocol discussions
 help / color / mirror / Atom feed
From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: Re: iperf
Date: Sat, 21 Jul 2007 17:13:18 +0000	[thread overview]
Message-ID: <200707211813.18317@strip-the-willow> (raw)
In-Reply-To: <5bc4c4570707171213v6eb89545y5970e471345cc3f8@mail.gmail.com>

Thanks - what I did is put the whole thing into a useable format. 

There is now a combined iperf source tarball which has 
     (1) DCCP support, 
     (2) -b switch for CBR mode, 
     (3) TCP pluggable congestion control, and 
     (4) continuous test runs 

all integrated. With the exception of (2), most of these are from your 
patches. The combined tarball comes via

wget http://www.erg.abdn.ac.uk/users/gerrit/dccp/apps/iperf/zip/iperf-2.0.2_DCCP-patched-CBR-continuous.tar.bz2

I have added description on the CBR mode on the DCCP testing pages on

 http://linux-net.osdl.org/index.php/DCCP_Testing#Testing_with_constant_bitrate


The UDP-Lite variant of iperf has been banned into the UDP-Lite tarball.

|  The only comment on your version is that you remove WIN32 code, and
|  rename some existing options. I had a hope that the code could get
|  merged upstream but my emails to the iperf list haven't succeeded in
|  this (probably because the CAIDA project has no funding).
I fully agree with your comment, but there were reasons - I figured that it will
take a long time until Windows supports both DCCP, plug-able TCP congestion control,
and UDP-Lite; and I found that the code (if it is going to be used under Lunix only)
is much more readable. I can separate out the windows changes into a standalone 
patch, but for the moment I'd much rather put in effort into the test tree.

There is only one flag change:
 * -d  /  --dualtest   becomes `-2' / `--dualtest'
 * -d  /  --dccp       becomes the new switch for DCCP

The other additions were
 * -A <algo>  chooses TCP congestion control algorithm
 * -b now works for UDP and DCCP in the same manner

 
Gerrit

      parent reply	other threads:[~2007-07-21 17:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 19:13 iperf 
2007-07-17 20:18 ` iperf Ian McDonald
2007-07-19 12:42 ` iperf Patrick
2007-07-19 12:58 ` iperf Gerrit Renker
2007-07-19 13:02 ` iperf Burak Gorkemli
2007-07-19 16:57 ` iperf Patrick
2007-07-19 23:39 ` iperf Ian McDonald
2007-07-19 23:41 ` iperf Ian McDonald
2007-07-19 23:45 ` iperf Ian McDonald
2007-07-20  5:00 ` iperf Ian McDonald
2007-07-20 12:35 ` iperf Gerrit Renker
2007-07-20 12:42 ` iperf Gerrit Renker
2007-07-20 12:55 ` iperf Gerrit Renker
2007-07-20 17:53 ` iperf Gerrit Renker
2007-07-20 20:38 ` iperf Ian McDonald
2007-07-20 20:40 ` iperf Ian McDonald
2007-07-20 20:41 ` iperf Ian McDonald
2007-07-21 17:13 ` Gerrit Renker [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200707211813.18317@strip-the-willow \
    --to=gerrit@erg.abdn.ac.uk \
    --cc=dccp@vger.kernel.org \
    /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