From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 60754 invoked by alias); 29 Apr 2015 22:41:17 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 60706 invoked by uid 89); 29 Apr 2015 22:41:15 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.3 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 X-HELO: dytn-smtp1.trimble.com Received: from dytn-smtp1.trimble.com (HELO dytn-smtp1.trimble.com) (155.63.0.78) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Wed, 29 Apr 2015 22:41:14 +0000 Received: (qmail 12762 invoked by uid 502); 29 Apr 2015 18:41:12 -0400 X-Qmail-Scanner-Diagnostics: from 10.1.75.25 by dytn-smtp1.trimble.com (envelope-from , uid 488) with qmail-scanner-2.11 (clamdscan: 0.98.6/20392. avast: v3.2.1/150428-1. sophie: 3.06/3.60.0/5.14. spamassassin: 3.4.0. Clear:RC:1(10.1.75.25):. Processed in 0.008415 secs); 29 Apr 2015 22:41:12 -0000 Received: from unknown (HELO usd-cas-02.trimblecorp.net) (10.1.75.25) by dytn-smtp1.trimble.com with (AES128-SHA encrypted) SMTP; 29 Apr 2015 18:41:12 -0400 Received: from USD-MBX-01.trimblecorp.net ([fe80::59c3:60a9:bdbe:d34f]) by usd-cas-02.trimblecorp.net ([fe80::c923:9ef7:29b7:871%16]) with mapi id 14.03.0235.001; Wed, 29 Apr 2015 18:41:12 -0400 From: Weili Yao To: "ecos-discuss@ecos.sourceware.org" Date: Wed, 29 Apr 2015 22:41:00 -0000 Message-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes Subject: [ECOS] Questions about CYGPKG_NET_MEM_USAGE and CYGPKG_NET_MEMPOOL_SIZE X-SW-Source: 2015-04/txt/msg00011.txt.bz2 Hello All, We have devices that are using ECOS BSD_TCP stack for networking. The de= vice supports multiple interfaces such as Ethernet on "eth0", ppp, and Wi-F= i 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_MAXS= OCKETS to 100. In our LAN, we occasionally see no free net_mem_pool, and al= so 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_SI= ZE 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