Re: DAST: Iperf - iperf receive data verify - amit.kumar --at-- intel.com (fwd)

["John S. Estabrook" <jestabro --at-- ncsa.uiuc.edu>]

Regarding the second question, the iperf server spawns (multiple) threads 
for _each_ connection, assuming that you are running in multi-threaded 
mode; this is the default.

There were known problems with threads in the early 2.0.* versions; these 
are fixed in 2.0.2.

If you are running iperf-2.0.2 and you have not configured with 
--disable-threads, then we shall have to search for the source of your 
problem.

Regarding the first point, it seems like a reasonable request; current 
iperf development is sporadic, but we'll add it to the list.

Thanks.

On Tue, 9 May 2006, John S. Estabrook wrote:

> ---------- Forwarded message ----------
> Date: Tue, 9 May 2006 12:37:39 -0500
> From: Apache <apache --at-- ncsa.uiuc.edu>
> To: amit.kumar --at-- intel.com
> Subject: DAST: Iperf - iperf receive data verify - amit.kumar --at-- 
> intel.com
>
>
> Contacting DAST re: Request for information about Iperf
> From: Amit Kumar <amit.kumar --at-- intel.com>
>
> Subject: iperf receive data verify
>
> Question/Comment:
> Hi,
>
> My name is Amit and I work in Performance Networking Lab at Intel 
> Corporation. I've been using Iperf for my performance measurement tests for a 
> couple of weeks and there's one feature that I would love to have.
>
> - Is there an option to verify data that is received on Server side? This 
> verification may not be very clever, just reading each byte and modifying a 
> counter will be of great use. I wonder if such an option is already present 
> or in your development pipeline?
>
> - My second question is: How are multiple TCP connections on the server side 
> handled? If I run 8 connections per port, I see only one iperf process 
> running on the system. Is iperf not spawning multiple OS threads to receive 
> data in parallel for all 8 connections?
>
> Will appreciate your answers.
>
> Thanks
> Amit

John S. Estabrook
jestabro --at-- ncsa.uiuc.edu
jestabro --at-- dast.nlanr.net