Hello everyone,

I'd like to take a minute to explain what has been going on with Iperf and try
to set expectations and gather some momentum.

I have been less than responsive as the maintainer for Iperf and for that I
apologize.  I'm afraid life has been keeping me altogether too busy lately.
However, there has been some progress that you may be unaware of.

Last year I decided that Iperf as it stood had become unmaintainable and
started rewriting it.  I made some decent progress and had a summer student
who made even more progress.  That code is fairly close to being ready and is
much cleaner than the current code.

That said, the current Iperf is used by many, many people all over the planet.
The last burst of messages on this list show that there is continuing interest
in Iperf.  I have taken what I deem to be the most crictical patches that have
accumulated and incorporated them into the SVN trunk.  I will be sending out
an announcement of the 2.0.5b1 release momementarily.

Here's the game plan.  I will take whatever other important bug and
performance patches and incorporate them into the 2.0.5 release.  I'm not
interested in adding new features to the Iperf 2.0.x train.   I will consider
Windows patches in the tracker, but they're pretty large and I haven't had a
chance to look at them.  Also, I don't have a Windows development environment.

I plan to cut the 2.0.5 release of Iperf no later than the end of next week,
so if you have changes that you really want to see please get them to me ASAP.  

As to new features I will definitely consider them for Iperf 3.  Iperf 3 as it
stands does TCP testing pretty well but UDP isn't implemented yet.  Iperf 3 is
a lot cleaner and simpler.  Presently, Iperf 3 uses select() for multiple
streams rather than threads, although threading might get added sometime in
the future.  It has been designed from the beginning as a library with the
"classic" Iperf command line syntax as the first application of that library.
You can find Iperf 3 at:

http://code.google.com/p/iperf/

If you have feature requests or patches for Iperf 3 please use the tracker
there.

Finally, I am actively looking for a summer student to work with to finish up
Iperf 3.  If you're interested or know a student who would be interested,
please contact me.

I do apologize for the long period of inactivity.  

Cheers,

Jon
-- 
Jon M. Dugan <jdu...@es.net>
ESnet Network Engineering Group
Lawrence Berkeley National Laboratory

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Iperf-users mailing list
Iperf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/iperf-users

Reply via email to