I made some recent changes to netperf to workaround what is IMO a bug in the
Solaris getaddrinfo() where it will clear the ai_protocol field even when one
gives it a protocol in the hints.
[If you happen to be trying to use the test-specific -D to set TCP_NODELAY in
netperf on Solaris, you might want to grab netperf TOT to get this workaround as
it relates to issues with setting TCP_NODELAY - modulo what it will do to being
able to run the netperf SCTP tests on Linux...]
In the process though I have stumbled across what appears to be a bug (?) in
"Linux" getaddrinfo() - returning a -7 EAI_SOCKTYPE if given as hints
SOCK_STREAM and IPPROTO_SCTP - this on a system that ostensibly supports SCTP.
I've seen this on RHAS4U4 as well as another less well known distro.
I'm about to see about concocting an additional workaround in netperf for this,
but thought I'd ask if my assumption - that getaddrinfo() returning -7 when
given IPPROTO_SCTP - is indeed a bug in getaddrinfo(). Or am I just woefully
behind in patches or completely offbase on what is correct behaviour for
getaddrinfo and hints?
FWIW, which may not be much, Solaris 10 06/06 seems content to accept
IPPROTO_SCTP in the hints.
thanks,
rick jones
http://www.netperf.org/svn/netperf2/trunk/
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
