From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23332 invoked by alias); 28 Apr 2013 12:12:51 -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 23321 invoked by uid 89); 28 Apr 2013 12:12:50 -0000 X-Spam-SWARE-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 Received: from relay03.alfahosting-server.de (HELO relay03.alfahosting-server.de) (109.237.142.239) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Sun, 28 Apr 2013 12:12:48 +0000 Received: by relay03.alfahosting-server.de (Postfix, from userid 1001) id 7A9D432C0545; Sun, 28 Apr 2013 14:12:46 +0200 (CEST) X-Spam-DCC: : Received: from alfa3017.alfahosting-server.de (alfa3017.alfahosting-server.de [109.237.140.28]) by relay03.alfahosting-server.de (Postfix) with ESMTP id 627A832C0528; Sun, 28 Apr 2013 14:12:44 +0200 (CEST) Received: from itrrrauch (p578a450a.dip0.t-ipconnect.de [87.138.69.10]) by alfa3017.alfahosting-server.de (Postfix) with ESMTPA id 3C2FF2934364; Sun, 28 Apr 2013 14:12:44 +0200 (CEST) From: "Richard Rauch" To: "'Laurie Gellatly'" Cc: References: <001201ce4404$f89d4f20$e9d7ed60$@netic.com> <001501ce4406$9f7a0670$de6e1350$@itrgmbh.de> <6AE794FE-711D-410C-B747-335C163616B7@netic.com> In-Reply-To: <6AE794FE-711D-410C-B747-335C163616B7@netic.com> Date: Sun, 28 Apr 2013 12:12:00 -0000 Message-ID: <001601ce4409$b090d800$11b28800$@itrgmbh.de> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Virus-Checker-Version: clamassassin 1.2.4 with ClamAV 0.97.3/17107/Sun Apr 28 12:41:52 2013 Subject: AW: AW: [ECOS] FreeBSD not always releasing ACK MBUFs X-SW-Source: 2013-04/txt/msg00033.txt.bz2 Hmm, hard to say, what exactely is the reason for your problems. The stack is well known for having several problems regarding mbufs and oth= ers...but I thought, the commercial eCosPro Version, you are using, should = contain an improved stack version! One of our porting projects was for Atmel AT91SAM9G45 and our customer Soft= ing provided a bunch of improvements. You could compare your version with our version, available at http://tiprom= .itrgmbh.com/projects/ecos-on-atmel9g45=20 Maybe it's helpful! Richard > -----Urspr=C3=BCngliche Nachricht----- > Von: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss- > owner@ecos.sourceware.org] Im Auftrag von Laurie Gellatly > Gesendet: Sonntag, 28. April 2013 13:56 > An: Richard Rauch > Cc: > Betreff: Re: AW: [ECOS] FreeBSD not always releasing ACK MBUFs >=20 > FreeBSD. How did I miss that important fact??? >=20 > ...Laurie:{) > +61 416 114419 >=20 >=20 > On 28/04/2013, at 9:50 PM, "Richard Rauch" wrote: >=20 > > Hello, > > > > which TCP/IP Stack are you using? FreeBSD or lwIP? > > > > Richard > > > > ITR GmbH > > web: http://www.itrgmbh.com > > email: info@itrgmbh.com > > > > > >> -----Urspr=C3=BCngliche Nachricht----- > >> Von: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss- > >> owner@ecos.sourceware.org] Im Auftrag von Laurie Gellatly > >> Gesendet: Sonntag, 28. April 2013 13:39 > >> An: ecos-discuss@sourceware.org > >> Betreff: [ECOS] FreeBSD not always releasing ACK MBUFs > >> > >> Hi All, > >> I'm using eCosPro from pre eCos 3.0 to serve web pages with embedded > >> images, CSS and javascripts. > >> Some pages are set to refresh their content and eventually the > >> application runs out of MBUFs and restarts. > >> I can use my own web server or the CYGPKG_HTTPD server with the same > >> result. > >> > >> I used the CYGPKG_HTTPD server on port 81 to monitor network stats. > >> What I find is that the =E2=80=98HEADER=E2=80=99 type MBUFs grow and n= ever shrink, > >> eventually running out of MBUFs completely. > >> The amount of growth in each iteration varies. > >> When I dump the data in the HEADER MBUFs (modified support.c to print > >> these short MBUFs) and compared them to the network traffic seen by > >> wireshark I have confirmed that the HEADERs are correct ACK packets > >> sent at the close of various HTTP get sequences. > >> For some reason they are not being released. > >> > >> I also found that the number of timeout entries (NTIMEOUTS) in > >> timeout.c (default 8) is WAY below what is needed (about 70 being used= ). > >> > >> I'm thinking it's something to do with TIME_WAIT not closing the > >> tcpcb when it should. > >> > >> Has anyone seen this before or can suggest a way to troubleshoot this? > >> > >> Thanks ...Laurie:{) > >> > >> > >> > >> > >> -- > >> Before posting, please read the FAQ: > >> http://ecos.sourceware.org/fom/ecos > >> and search the list archive: > >> http://ecos.sourceware.org/ml/ecos-discuss > > > > > > >=20 > -- > Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss