On Thu, Jul 25, 2013 at 04:43:52PM +0200, Michal Privoznik wrote:
> On 25.07.2013 16:37, Daniel P. Berrange wrote:
> > On Thu, Jul 25, 2013 at 04:23:32PM +0200, Michal Privoznik wrote:
> >> Currently, even if max_client limit is hit, we accept() incoming
> >> connection request, but close it immedi
On 25.07.2013 16:37, Daniel P. Berrange wrote:
> On Thu, Jul 25, 2013 at 04:23:32PM +0200, Michal Privoznik wrote:
>> Currently, even if max_client limit is hit, we accept() incoming
>> connection request, but close it immediately. This has disadvantage of
>> not using listen() queue. We should acc
On Thu, Jul 25, 2013 at 04:23:32PM +0200, Michal Privoznik wrote:
> Currently, even if max_client limit is hit, we accept() incoming
> connection request, but close it immediately. This has disadvantage of
> not using listen() queue. We should accept() only those clients we
> know we can serve and
Currently, even if max_client limit is hit, we accept() incoming
connection request, but close it immediately. This has disadvantage of
not using listen() queue. We should accept() only those clients we
know we can serve and let all other wait in the (limited) queue.
---
src/rpc/virnetserver.c
