public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS]  Re: "PANIC: zinit: Out of memory" when num sockets 	increased to 64
Date: Wed, 09 Apr 2008 11:51:00 -0000	[thread overview]
Message-ID: <ftia2i$5aj$1@ger.gmane.org> (raw)
In-Reply-To: <20080408202951.GH3552@lunn.ch>

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?

-- 
Grant Edwards                   grante             Yow! Hmmm ... a CRIPPLED
                                  at               ACCOUNTANT with a FALAFEL
                               visi.com            sandwich is HIT by a
                                                   TROLLEY-CAR ...


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

  parent reply	other threads:[~2008-04-09 11:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-08 20:30 [ECOS] " Grant Edwards
2008-04-08 20:38 ` Andrew Lunn
2008-04-09  8:20   ` [ECOS] " Grant Edwards
2008-04-09 11:51   ` Grant Edwards [this message]
2008-04-09 12:08     ` Gary Thomas
2008-04-09 12:25       ` Grant Edwards
2008-04-09 16:10         ` Gary Thomas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='ftia2i$5aj$1@ger.gmane.org' \
    --to=grante@visi.com \
    --cc=ecos-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).