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: Fri, 20 Jul 2007 17:53:28 +0000	[thread overview]
Message-ID: <200707201853.28744@strip-the-willow> (raw)
In-Reply-To: <5bc4c4570707171213v6eb89545y5970e471345cc3f8@mail.gmail.com>

Ian,

I also cleaned up my patch set to
 * completely remove UDP-Lite from all other patches
 * shift UDP-Lite to the end (as fourth patch)
 * I have shamelessly stolen your `continuous' patch and integrated as patch #3
 * result (patches 1..3) compiles without error or problems on a brandnew 
   installation of linux (with unmodified kernel headers)
 * I haven't had time to look through your code, but I think we should put
   out one combined client for testing purposes.

I am not fussy who's it is we are using - the code is after all yours. I just
polished it a bit up and made sure that the -b switch also works for DCCP.

And I have found it quite a useful switch for testing, indeed.

Results are on http://www.erg.abdn.ac.uk/users/gerrit/dccp/apps/iperf/patches/
       (src:   http://www.erg.abdn.ac.uk/users/gerrit/dccp/apps/iperf/zip/ )
Gerrit

Quoting Ian McDonald:
|  OK. I've hacked my iperf version around a bit to get closer to Gerrit's.
|  
|  What I've done:
|  - ported more of his code over
|  -- renaming/shifting code
|  -- fix service code handling to allow network byte order and correct name
|  -- merged using -b option for DCCP (NB gives an error at end but seems
|  to be working OK)
|  
|  Our code still differs a bit e.g. I don't support UDP Lite yet.
|  
|  So if you want unlimited run time and -b together then you want my
|  tree, otherwise Gerrit's is probably better. I'm sure Gerrit can port
|  my unlimited run time easily to his tree if he wants.
|  
|  My patches are at:
|  http://wand.net.nz/~iam4/iperf/
|  
|  Ian

  parent reply	other threads:[~2007-07-20 17:53 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 ` Gerrit Renker [this message]
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 ` iperf Gerrit Renker

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=200707201853.28744@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