From: Weili Yao <weili_yao@trimble.com>
To: "ecos-discuss@ecos.sourceware.org" <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Questions about CYGPKG_NET_MEM_USAGE and CYGPKG_NET_MEMPOOL_SIZE
Date: Wed, 29 Apr 2015 22:41:00 -0000 [thread overview]
Message-ID: <B53EF7F1B3FACA45A95C31FB02F38C5107F834@usd-mbx-01.trimblecorp.net> (raw)
Hello All,
We have devices that are using ECOS BSD_TCP stack for networking. The device supports multiple interfaces such as Ethernet on "eth0", ppp, and Wi-Fi on "eth1" and "eth2". In the ecos.ecc, we set the CYGPKG_NET_MEM_USAGE to 640000 bytes, CYGPKG_NET_MEMPOOL_SIZE to 300000 bytes, and CYGPKG_NET_MAXSOCKETS to 100. In our LAN, we occasionally see no free net_mem_pool, and also we see no free sockets.
My questions are:
1) What will happen when the system runs out of the configured NET_MEM_POOL memory? Will it corrupt the network stacks?
2) Since we see the system sometime runs out of sockets, we intend to double CYGPKG_NET_MAXSOCKETS to 200, then how much is CYGPKG_NET_MEMPOOL_SIZE needed and how much should I set CYGPKG_NET_MEM_USAGE to?
Any suggestions and insights are welcome!
Thank you a lot!
Weili
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
reply other threads:[~2015-04-29 22:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=B53EF7F1B3FACA45A95C31FB02F38C5107F834@usd-mbx-01.trimblecorp.net \
--to=weili_yao@trimble.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).