From: "Marco Monguzzi" <marco@sitek.it>
To: "Grant Edwards" <grante@visi.com>
Cc: <ecos-discuss@sourceware.cygnus.com>
Subject: RE: [ECOS] problems with MBUFs (TCP/IP stack)
Date: Mon, 10 Jul 2000 10:21:00 -0000 [thread overview]
Message-ID: <NCBBKIOHEKNFDFBEBPNHAEFMDOAA.marco@sitek.it> (raw)
In-Reply-To: <20000710155038.A1897@visi.com>
> I've set up a test script that starts and stops my host-end
> application, and so far have about 500 TCP/IP open/close cycles
> without problems. I haven't been printing MBUF counters, but I
> haven't seen any panics or anything else odd. After I let this
> run for a while longer, I might have to try it with the program
> from the test suite.
I would appreciate whether you could provide me with you test programs.
I will try them on my target. A bit more on the behavior we observe with
server_test.c: we found that the problem is in the "close connection
sequence"
(close(client); Line 128). One MBUF remains allocated because not all the
needed
"free functions" are called. In detail, close() does not call tcp_close().
The latter should call the free() for the tcp_template that we think remains
allocated.
> Is the source for the eCos port of the goahead publically
> available? Sometime in the next few weeks adding an HTTP
> server is going to end up at the top of my list of things to
> do.
The porting is distributed with 2.1 release version by goahead software.
Regards,
Marco
next prev parent reply other threads:[~2000-07-10 10:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-08 5:54 Marco Monguzzi
2000-07-08 8:26 ` Grant Edwards
2000-07-08 11:45 ` Marco Monguzzi
2000-07-08 12:05 ` Marco Monguzzi
2000-07-10 8:50 ` Grant Edwards
2000-07-10 9:53 ` Gary Thomas
2000-07-10 10:21 ` Marco Monguzzi [this message]
2000-07-10 10:33 ` Grant Edwards
2000-07-10 10:41 ` Gary Thomas
2000-07-10 11:18 ` Marco Monguzzi
2000-07-10 13:03 ` Grant Edwards
2000-07-11 3:45 ` Hugo 'NOx' Tyson
2000-07-11 8:38 ` Marco Monguzzi
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=NCBBKIOHEKNFDFBEBPNHAEFMDOAA.marco@sitek.it \
--to=marco@sitek.it \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=grante@visi.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).