Re: [ECOS] Not accepting the More than 95 connections in eCos 2.0

[Nick Garnett <nickg at ecoscentric dot com>]

"Vedaraman Sethuraman (IE10)" <Vedaraman.Sethuraman@honeywell.com> writes:

> Hello Gary,
> 
> I have some problems handling many requests to a tcp server in eCos 2.0.
> 
> I am using the following
> 	Free BSD stack.
> 	i386 Arch.
> 
> I have simple socket program(server) which accepts the connection, prints
> the client 
> data and disconnects.
> 
> Server : eCos.
> Client : Windows.
> 
> The program works for a while i.e(for around 95 connection) after it
> reaches 95 its not accepting the clients anymore.  It's happening
> every time.

How rapidly do you make these connections? Closed sockets do not
release all their memory immediately. It is a requirement of the TCP
protocol that it linger for some time to retransmit its last packet in
case it got lost. If you wait a couple of minutes you will see all the
memory get released and you will be able to make more connections.

In a BSD installation, with megabytes of RAM, this doesn't matter
much, and the RAM usage will find a level consistent with the turnover
rate of the connections. In a restricted RAM environment you will hit
the limits earlier.

-- 
Nick Garnett                    eCos Kernel Architect
http://www.ecoscentric.com/     The eCos and RedBoot experts


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss