From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: <kenkyee@excite.com>, <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] bind() shouldn't return EAGAIN for an error
Date: Thu, 27 Sep 2012 03:07:00 -0000 [thread overview]
Message-ID: <BAY146-W57E775E85F9121CD3363CBE4830@phx.gbl> (raw)
In-Reply-To: <20120924172129.16356@web003.roc2.bluetie.com>
Hi Ken,
> AFAIK, bind() should never return EAGAIN for an error:
> http://homepages.cwi.nl/~aeb/linux/man2html/man2/bind.2.html
In the BSD manpages, EAGAIN means, you are out of memory, see for instance:
http://www.unix.com/man-page/FreeBSD/2/bind/
There is a configurable memory pool for variable size objects in the bsd stack.
I'd suggest you should increase CYGPKG_NET_MEMPOOL_SIZE
and check that too:
CYGSEM_MEMALLOC_ALLOCATOR_VARIABLE_COALESCE should be 1 (default)
Regards
Bernd Edlinger.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2012-09-27 3:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 21:21 Ken Yee
2012-09-27 3:07 ` Bernd Edlinger [this message]
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=BAY146-W57E775E85F9121CD3363CBE4830@phx.gbl \
--to=bernd.edlinger@hotmail.de \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=kenkyee@excite.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).