Skip to Content.
Sympa Menu

ndt-dev - [ndt-dev] Re: [Web10g-user] NDT Web10G Patch

Subject: NDT-DEV email list created

List archive

[ndt-dev] Re: [Web10g-user] NDT Web10G Patch

Chronological Thread 
  • From: rapier <>
  • To: Richard Sanger <>
  • Cc:
  • Subject: [ndt-dev] Re: [Web10g-user] NDT Web10G Patch
  • Date: Wed, 23 Jan 2013 13:13:52 -0500

"The middlebox test's use of sequence numbers assumes that TCP Reno is being used." So I'll have the guy who did the work on the CUBIC implementation look into this. It might require some reworking depending on how sequence numbers are used in the different congestion control algorithms. I don't see this as being a show stopper though.

Getting away from RENO is pretty important considering that the default is now CUBIC.

I'll let you know what we find out and thanks for splitting the patches up.


On 1/22/13 6:13 PM, Richard Sanger wrote:
Hi Chris,

Good to here you got this compiling, yeah the I2util is a bit of a pain.

As for requiring reno this is not a KIS Web10G/Web100 requirement,
rather to do with the middlebox/ndt test itself. - under

However cubic could be a perfectly fine substitute. I don't know too
much about the differences reno vs cubic myself nor why reno is a
requirement of ndt tests. If someone who knows a bit more about this
could weigh in it would be appreciated.

As for porting process, I'll try do a write up when I get some time -
since its probably useful for everyone.


On Wed, Jan 23, 2013 at 11:34 AM, rapier

Hey, I got it to build. I was making a stupid mistake at first by
copying over I2util before I ran autoreconf. It seems that following
the instructions is useful. Anyway, I'm going to start running some
tests soon by comparing results between web100 and web10g ndt servers.

Hopefully the warning about requiring reno for accurate results
isn't entirely true since we've extended the KIS to support BIC,

I'll let you know more after I get some data together.

Thanks again for doing this, you have no idea how much time you
saved us on this.

As for Aaron's request about splitting up the patch. That is,
admittedly, a pain in the butt. If you can do that it would help
with the adoption quite a bit though. Our end goal is to have this
be a central part of the perfSonar Web10G deployment (which will
eventually obsolete the Web100 deployment that is the base now). So
if nothing else you'll know that the work you did is being used by
the community.

Also, when you have time I may want to talk to you a bit about the
porting process. I'm the project leader (but not developer) and
we're really trying to get an idea of what it's like using the new API.

Thanks again!


On 1/22/13 12:16 AM, Richard Sanger wrote:

Or there is a .tar of the web10G version here
the patch already applied.

On Tue, Jan 22, 2013 at 5:50 PM, Richard Sanger





The patch is for the current svn version being r796
retrieved from
here .
Make sure you run autoreconf (automake/autoconf) to build new
configuration files, these have been changed. Then remember
to copy
I2Util library (From the release) into the ndt/ folder
before running ./configure. If you have the web10g/web100
installed it should build the corresponding versions of the


On Tue, Jan 22, 2013 at 11:01 AM, rapier




Quick question - which version of NDT did you build the
against? Applying it against (the latest I've
been able
to find) is producing a lot of failures.


On 1/17/13 1:16 AM, Richard Sanger wrote:


As part of an internship at WAND, I've been working
on a
web10g version
of ndt.

The patch is attached.
I've also got some Web10g patched linux kernels for
Debian(squeeze or
wheezy should work) here.




NOTE: The kernel needs a slight modification to the
kernel patch.
Which is included in the Google drive folder above.

I've incorporated Web10G into the code in such a
way that
both the
web100srv and web10g can be built. Besides some bug
the web100srv
is unchanged. The configuration process should
detect web100
and web10g
libraries and build accordingly. Web10G variable
logging is not
implemented - this shouldn't have any effects on
the results.

For the most part the client hasn't been changed,
so an old
client can
connect without issues. The only things that could
go wrong
with an old
client are TCP Timestamps/ECN may be incorrectly
detected as on.

This patch also includes a few fixes for both
clients and
including those I logged as issues #69 #70 #71 #73.

Along with web10g this adds code in
ndt/src/kernel_* files
which will
check some of the kernel configuration for a Web10G
and print
warnings about incorrect configuration.(If the
server is run
with -k
option these will be corrected).

Look at ndt/WEB10G README for more information.

I would be great to get this incorporated into the
ndt trunk (or
branch). Although the Web10G code still needs more
the web100
parts of the code are unchanged.

Send me an email if you have any issues all
feedback is welcome.


Web10g-user mailing list







Archive powered by MHonArc 2.6.16.

Top of Page