This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Re: "PANIC: zinit: Out of memory" when num sockets increased to 64


Grant Edwards wrote:
On 2008-04-08, Andrew Lunn <andrew@lunn.ch> wrote:
So there's well over 15MB of unallocated RAM. That seems like
more than enough RAM to handle 64 sockets.
Why am I getting a panic on startup?
The network stack has its own memory pool. See

CYGPKG_NET_MEM_USAGE, CYGPKG_NET_MEMPOOL_SIZE, CYGPKG_NET_MBUFS_SIZE,
CYGPKG_NET_MBUFS_SIZE.

Several other people seem to have tripped over this bug. IMO, the problem is that the default value takes the number of sockets into account, and the description claims that value is guaranteed to allow the network stack to start up.

One presumes that the minimum value required for stack startup
could be calculated at configure time based on the max number
of sockets.  Since that isn't being done, should I submit a
patch that would change the description so that it doesn't say
that it is?


Or, better yet, improve the CDL so it behaves as folks expect :-)


--
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]