There is a very serious repurcussion to allowing this be increased in
any form, people won't fix their code if you just give them this
The new connection backlog controlled by an upper limit of
SOMAXCONN is a "buffer" between the kernel and userspace.
It is _NOT_ a permanent storage area inside the kernel for new
connections. Once people writing these apps start thinking about it
as a buffer (ie. think "temporary"), the thought to increase SOMAXCONN
will occur less often in their minds.
I have never been shown a legitimate argument for increasing
David S. Miller
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/