[netperf-talk] help needed

[Rick Jones]

Srinivasan S wrote:
> Hi Rick,
> 
> With Strace even after 40 minuts I don't get 10 Sec timeout, I tried with -l 1 option 
> trying to run for one second and even after 10 minuts it does not end. Is it normal 
> with strace?

Sometimes I wonder if _anything_ is ever normal with strace...  It would be good 
to file that as an strace defect against the distro you are using.

> 
> With the debugging option I have the following 
> 
> 1. At the server side
> ---------------------
> 
> -----------------------------------------start of log -------------------------
> recv_request: received 256 bytes of request.
> netserver: recv_tcp_stream: entered...
> recv_tcp_stream: setting the response type...
> recv_tcp_stream: the response type is set...
> recv_tcp_stream: requested alignment of 8
> complete_addrinfo using hostname 0.0.0.0 port 0 family AF_INET type SOCK_STREAM prot IPPROTO_TCP flags 0x0
> getaddrinfo returned the following for host '0.0.0.0' port '0' family AF_INET
>         cannonical name: '0.0.0.0'
>         flags: 2 family: AF_INET: socktype: SOCK_STREAM protocol IPPROTO_TCP addrlen 16
>         sa_family: AF_INET sadata: 0 0 0 0 0 0
> create_data_socket: socket 2 obtained...
> netperf: set_sock_buffer: send socket size determined to be 16384
> netperf: set_sock_buffer: receive socket size determined to be 87380
> recv_tcp_stream: receive alignment and offset set...
> recv_tcp_stream: got 3.83549e+07 bytes
> recv_tcp_stream: got 25983 recvs
> recv_tcp_stream: test complete, sending results.
>                  bytes_received 3.83549e+07 receive_calls 25983
>                  len 0

OK, so we see that the netserver has been receiving data.  that is good.

> recv_request: received 0 bytes of request.
> recv_request: remote requested shutdown of control
> -----------------------------------------end of log -------------------------
> 
> 2. At the netperf (target) side
> -------------------------------
> 
> -----------------------------------------start of log -----------------------
> 
> # ./netperf -H 172.20.33.217,4 -L 172.20.38.31,4 -d
> Program name: ./netperf
> Local send alignment: 8
> Local recv alignment: 8
> Remote send alignment: 8
> Remote recv alignment: 8
> Report local CPU 0
> Report remote CPU 0
> Verbosity: 1
> Debug: 1
> Port: 12865
> Test name: TCP_STREAM
> Test bytes: 0 Test time: 10 Test trans: 0
> Host name: 172.20.33.217
> 
> installing catcher for all signals
> Could not install signal catcher for sig 9, errno 22
> Could not install signal catcher for sig 19, errno 22
> remotehost is 172.20.33.217 and port 12865
> establish_control called with host '172.20.33.217' port '12865' remfam AF_INET
> 		local '172.20.38.31' port '0' locfam AF_INET
> getaddrinfo returned the following for host '172.20.33.217' port '12865' family AF_INET
> 	cannonical name: '172.20.33.217'
> 	flags: 2 family: AF_INET: socktype: SOCK_STREAM protocol IPPROTO_TCP addrlen 16
> 	sa_family: AF_INET sadata: 50 65 172 20 33 217
> getaddrinfo returned the following for host '172.20.38.31' port '0' family AF_INET
> 	cannonical name: '172.20.38.31'
> 	flags: 3 family: AF_INET: socktype: SOCK_STREAM protocol IPPROTO_TCP addrlen 16
> 	sa_family: AF_INET sadata: 0 0 172 20 38 31
> bound control socket to 172.20.38.31 and 0
> successful connection to remote netserver at 172.20.33.217 and 12865
> complete_addrinfo using hostname 172.20.33.217 port 0 family AF_UNSPEC type SOCK_STREAM prot IPPROTO_TCP flags 0x0
> getaddrinfo returned the following for host '172.20.33.217' port '0' family AF_UNSPEC
> 	cannonical name: '172.20.33.217'
> 	flags: 2 family: AF_INET: socktype: SOCK_STREAM protocol IPPROTO_TCP addrlen 16
> 	sa_family: AF_INET sadata: 0 0 172 20 33 217
> complete_addrinfo using hostname 0.0.0.0 port 0 family AF_UNSPEC type SOCK_STREAM prot IPPROTO_TCP flags 0x1
> getaddrinfo returned the following for host '0.0.0.0' port '0' family AF_UNSPEC
> 	cannonical name: '0.0.0.0'
> 	flags: 3 family: AF_INET: socktype: SOCK_STREAM protocol IPPROTO_TCP addrlen 16
> 	sa_family: AF_INET sadata: 0 0 0 0 0 0
> TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 172.20.33.217 (172.20.33.217) port 0 AF_INET
> create_data_socket: socket 4 obtained...
> netperf: set_sock_buffer: send socket size determined to be 16384
> netperf: set_sock_buffer: receive socket size determined to be 87380
> send_tcp_stream: send_socket obtained...
> recv_response: received a 256 byte response
> remote listen done.
> About to start a timer for 10 seconds.
> recv_response: received a 256 byte response
> remote results obtained
> calculate_confidence: itr  1; time 9.996183; res  0.000000
>                                lcpu -1.000000; rcpu -1.000000
>                                lsdm -1.000000; rsdm -1.000000
> Recv   Send    Send                          
> Socket Socket  Message  Elapsed              
> Size   Size    Size     Time     Throughput  
> bytes  bytes   bytes    secs.    10^6bits/sec  
> 
>  87380  16384  16384    10.00       0.00   
> shutdown_control: shutdown of control connection requested.
> # 
> 
> -----------------------------------------end of log -------------------------
> 
> I see that Test bytes: 0 and Test trans: 0 is this normal?

That is normal for a timed test.  If the test end conditions are set based on 
bytes or transactions then those would be non-zero.

> Also there are signal catcher error (error 22) why does it come and does it 
> effect the test?

In debug mode, netperf tries to catch all signals - some signals are 
uncatchable, hence the errors.

I was hoping to see the messages being exchanged in netperfs -d output - it may 
require a second -d in the command line.

rick jones

PS - as I am on netperf-talk, no need to cc me when netperf-talk is in the 
distribution.