[netperf-talk] Netperf client hanging

Rick Jones rick.jones2 at hp.com
Fri May 9 09:37:04 PDT 2008


Upakul Barkakaty wrote:
> Hi all,
> 
>  I was trying to set up the netperf client but its hanging after
> successful connection to remote netserver at 18.0.0.40 and 4000. Could
> someone please help out. Here is the Log:
> 
> 
>  -----------------------------------------------------------Log----------------------------------------------------------------------
> 
>  # ./netserver -d -4 -L 18.0.0.40,AF_INET -p 4000
>  Attempting to parse address family from AF_INET derived from AF_INET
>  WARNING! AF_INET not recognized as an address family, using AF_UNPSEC
>  Are you sure netperf was configured for that address family?
>  set_up_server called with host '18.0.0.40' port '4000' remfam 0
>  getaddrinfo returned the following for host '18.0.0.40' port '4000'
> family AF_UNSPEC
>          cannonical name: '(nil)'
>          flags: 1 family: AF_INET: socktype: SOCK_STREAM protocol
> IPPROTO_TCP add
>  rlen 16
>          sa_family: AF_INET sadata: 11 184 18 0 0 40
>  Starting netserver at port 4000
>  Starting netserver at hostname 18.0.0.40 port 4000 and family AF_UNSPEC
> 

Hmm, I dont' think I've ever seen that warning from the getaddrinfo call 
before - at least not for AF_INET.

Which rev of netperf is this?
Is the remote netserver the same rev?
Which OS and rev?

>  # ./netperf -4 -c -d -L 18.0.0.40 -p 4000,6000 -T lcpu -H 18.0.0.40
>  Processor affinity not available for this platform!
>  scan_sockets_args called with the following argument vector
>  ./netperf -4 -c -d -L 18.0.0.40 -p 4000 -T lcpu -H 18.0.0.40

"lcpu?"  If that is a shell variable, doesn't it need a "$" in front of it?

If the parms to -L and -H are the same, that suggests this is a loopback 
test - not sure if it wouldn't be better to just use -H localhost or 
take the default.  I don't think there is an (unmodified) TCP stack out 
there that will actually go-out to the NIC and back if that is what you 
are trying to accomplish.

>  Program name: ./netperf
>  Local send alignment: 8
>  Local recv alignment: 8
>  Remote send alignment: 8
>  Remote recv alignment: 8
>  Report local CPU 1
>  Report remote CPU 0
>  Verbosity: 1
>  Debug: 1
>  Port: 4000
>  Test name: TCP_STREAM
>  Test bytes: 0 Test time: 10 Test trans: 0
>  Host name: 18.0.0.40
> 
>  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
>  Could not install signal catcher for sig 65, errno 22
>  remotehost is 18.0.0.40 and port 4000
>  establish_control called with host '18.0.0.40' port '4000' remfam AF_INET
>                  local '18.0.0.40' port '6000' locfam AF_INET
>  getaddrinfo returned the following for host '18.0.0.40' port '4000'
> family AF_IN
>  ET
>          cannonical name: '18.0.0.40'
>          flags: 2 family: AF_INET: socktype: SOCK_STREAM protocol
> IPPROTO_TCP add
>  rlen 16
>          sa_family: AF_INET sadata: 15 160 18 0 0 40
>  getaddrinfo returned the following for host '18.0.0.40' port '6000'
> family AF_IN
>  ET
>          cannonical name: '18.0.0.40'
>          flags: 3 family: AF_INET: socktype: SOCK_STREAM protocol
> IPPROTO_TCP add
>  rlen 16
>          sa_family: AF_INET sadata: 23 112 18 0 0 40
>  bound control socket to 18.0.0.40 and 6000
>  successful connection to remote netserver at 18.0.0.40 and 4000


I would suggest a system call trace of netperf to see exactly what it is 
passing to the system calls.

happy benchmarking,

rick jones

> 
>  -----------------------------------------------------------Log----------------------------------------------------------------------
> 
> 



More information about the netperf-talk mailing list