As I see it, TIME_WAIT state is required for 2 reasons: to handle wandering duplicate packets (so a reincarnation of a connection will not be corrupted by these packets)
To handle last ack from active closer (client) not being received by remote. If that happened, the server which is in LAST_ACK state would retransmit its FIN (which may contain data also) so the client must be in TIME_WAIT state to handle that. If client is not in TIME_WAIT state, then it could only indicate to the server that data was maybe lost (with an RST). The first issue, requires a large timeout, and the TIME_WAIT timeout is currently 60 seconds on linux. That timeout effectively limits the connection rate between local TCP clients and a server to 32k/60s or around 500 connections/second. But that issue can't really happen when the client and server are on the same machine can it, and even if it could, the timeouts involved would be shorter. Now linux does have an (undocumented) /proc/sys/net/ipv4/tcp_tw_recycle flag to enable recycling of TIME_WAIT connections. This is global however and could cause problems in general for external connections. So how about auto enabling recycling for local connections? cheers, Pádraig. - 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
