public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Laurie Gellatly" <laurie.gellatly@netic.com>
To: "'Richard Rauch'" <rrauch@itrgmbh.de>
Cc: <ecos-discuss@sourceware.org>
Subject: RE: AW: [ECOS] FreeBSD not always releasing ACK MBUFs
Date: Mon, 29 Apr 2013 12:55:00 -0000	[thread overview]
Message-ID: <004701ce44d8$d880d6b0$89828410$@netic.com> (raw)
In-Reply-To: <001601ce4409$b090d800$11b28800$@itrgmbh.de>

Hi Richard,
Thanks again. But I didn't find anything that has helped.			...Laurie:{)

-----Original Message-----
From: ecos-discuss-owner@sourceware.org [mailto:ecos-discuss-owner@sourceware.org] On Behalf Of Richard Rauch
Sent: Sunday, 28 April 2013 10:13 PM
To: 'Laurie Gellatly'
Cc: ecos-discuss@sourceware.org
Subject: AW: AW: [ECOS] FreeBSD not always releasing ACK MBUFs

Hmm, hard to say, what exactely is the reason for your problems.
The stack is well known for having several problems regarding mbufs and others...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 Softing provided a bunch of improvements.
You could compare your version with our version, available at http://tiprom.itrgmbh.com/projects/ecos-on-atmel9g45
Maybe it's helpful!

Richard


> -----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:56
> An: Richard Rauch
> Cc: <ecos-discuss@sourceware.org>
> Betreff: Re: AW: [ECOS] FreeBSD not always releasing ACK MBUFs
> 
> FreeBSD. How did I miss that important fact???
> 
>         ...Laurie:{)
> +61 416 114419
> 
> 
> On 28/04/2013, at 9:50 PM, "Richard Rauch" <rrauch@itrgmbh.de> wrote:
> 
> > 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



--
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

  parent reply	other threads:[~2013-04-29 12:55 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 ` AW: " Richard Rauch
2013-04-28 11:55   ` Laurie Gellatly
2013-04-28 12:12     ` AW: " Richard Rauch
2013-04-28 20:43       ` Laurie Gellatly
2013-04-29 12:55       ` Laurie Gellatly [this message]
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='004701ce44d8$d880d6b0$89828410$@netic.com' \
    --to=laurie.gellatly@netic.com \
    --cc=ecos-discuss@sourceware.org \
    --cc=rrauch@itrgmbh.de \
    /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).