Re: your mail

From: Tom McNeal
Date: Thu Jun 16 2005 - 20:45:12 EST

I'll look at that. This occurs on all Linux platforms, including a generic
2.4.31 I downloaded from The user test is trivial, just doing
the nonblocking connect, the poll, the send, and then the close, in that loop.


Chris Wedgwood wrote:
On Thu, Jun 16, 2005 at 11:08:28PM +0000, trmcneal@xxxxxxxxxxx wrote:

I've been working with some tcp network test programs that have
multiple clients opening nonblocking sockets to a single server
port, sending a short message, and then closing the socket,
100,000 times. Since the socket is non-blocking, it generally
tries to connect and then does a poll since the socket is busy.
The test fails if the poll times out in 10 seconds. It fails
consistently on Linux servers but succeeds on Solaris servers; the
client is a non-issue unless its loopback on the Linux server.

where is the code for this? are you sure you're not overflowing the
listen backlog somewhere? that would show up in some cases but not
all depending on latencies and local scheduler behavior

Tom McNeal
Email: trmcneal@xxxxxxxxxxx
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at