Re: iperf

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



|  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)
This is an error - you need to support the -b option on the server as well. The
reason is that iperf, like ttcp, uses a kind of handshake to terminate datagram 
test runs. You didn't describe the error - was it something like `did not receive the
last ack after 10 tries'? If yes then the code needs to support -b on the server
as well. The bandwidth measurements are otherwise not accurate.

|  
|  Our code still differs a bit e.g. I don't support UDP Lite yet.
Are these the only differences? If yes then I am all for combining one patch 
and uploading it to the description of regression testing.

Over the time I have using -b (even if it does not solve the present problem
with bandwidth) a very useful diagnosis tool, iperf at full speed generates
a lot of noise.
-
To unsubscribe from this list: send the line "unsubscribe dccp" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [IETF DCCP]     [Linux Networking]     [Git]     [Security]     [Linux Assembly]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]

  Powered by Linux