Somnath kotur:
Hi Robin,
I am trying out the 'netstress' test while testing my 10G
NIC Driver , while the 12 hr stress test passes and then moves on to
the 'max sessions test' it invariably ends up in a situtation where an
odd session fails to connect initially ... like the MAX results are
always 2997/29998 out of 3000 sessions:Failed ...
There have been instances where i have seen the same pass as well... .
I tried recreating the same testcase by hand, i.e start netservers on
both SUT and client , run start_netperf.sh with appropriate
paramenters (1500 sessions) from client ,waited for a little while
and then did the other way around, ran start_netperf.sh from SUT ...
I got the following error msg 4 times :
netperf: data send error: Transport endpoint is not connected
i typed 'ps -A | grep netperf/netserve | wc -l ' on both the systems
and confirmed that the SUT was 4 netperf sessions short, I immediately
created 4 netperf sessions by hand with the same parameters as
expected in the test case and sure enough there were a total of 3K
sessions running and they all ran fine... Usually that's what seems to
be happening , there seems to some glitch while setting up the
sessions initially , but on trying it again ,they all seem to work
just fine..
Is this really a bug in the driver that i need to look at or is this
something not too serious?
Thanks
Somnath
Hi, Somnath
Yes, we've also encountered this small problem when testing 3000
sessions on 10G NIC, though everything is OK in 1G NIC driver. It seems
be a problem in netperf when creating multiple sessions. I suggest you
to use uperf to test it, it works well on a huge number of sessions, it
can be got from http://www.uperf.org/
We are also working on change our test suite nicdrv from based on
netperf to uperf.
An workaround is to configure the DRIVER_SPEED variable to 10G in
the config.vars file. (The default value is 1G)
Thanks,
Robin
_______________________________________________
networking-discuss mailing list
[email protected]
