From: "Richard Rauch" <rrauch@itrgmbh.de>
To: "'Laurie Gellatly'" <laurie.gellatly@netic.com>,
<ecos-discuss@sourceware.org>
Subject: AW: [ECOS] FreeBSD not always releasing ACK MBUFs
Date: Sun, 28 Apr 2013 11:50:00 -0000 [thread overview]
Message-ID: <001501ce4406$9f7a0670$de6e1350$@itrgmbh.de> (raw)
In-Reply-To: <001201ce4404$f89d4f20$e9d7ed60$@netic.com>
Hello,
which TCP/IP Stack are you using? FreeBSD or lwIP?
Richard
ITR GmbH
web: http://www.itrgmbh.com
email: info@itrgmbh.com
> -----Ursprüngliche 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 ‘HEADER’ type MBUFs grow and never 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
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2013-04-28 11:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-28 11:39 Laurie Gellatly
2013-04-28 11:50 ` Richard Rauch [this message]
2013-04-28 11:55 ` AW: " Laurie Gellatly
2013-04-28 12:12 ` AW: " Richard Rauch
2013-04-28 20:43 ` Laurie Gellatly
2013-04-29 12:55 ` Laurie Gellatly
2013-05-04 13:11 ` Laurie Gellatly
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='001501ce4406$9f7a0670$de6e1350$@itrgmbh.de' \
--to=rrauch@itrgmbh.de \
--cc=ecos-discuss@sourceware.org \
--cc=laurie.gellatly@netic.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).