public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: Marco Monguzzi <marco@sitek.it>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] problems with MBUFs (TCP/IP stack)
Date: Mon, 10 Jul 2000 13:03:00 -0000	[thread overview]
Message-ID: <20000710200356.A3304@visi.com> (raw)
In-Reply-To: <20000710155038.A1897@visi.com>

On Mon, Jul 10, 2000 at 03:50:38PM -0500, Grant Edwards wrote:

> 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'm currently running the server_test program on my target
board and have done 1000+ connections with no problems.  I'm
running eCos 1.3.1 and networking package version 1.0b1 w/ some
mutex patches from sometime in April.

I tried out a CVS snapshot a week or so ago and saw one or two
"null mbuf" panics (which the mutex patches were to have
fixed).  The CVS version and my patched 1.0b1 behaved the same
in respect the bug I was tracking down, so I continued using my
patched 1.0b1 and have not had time to look into the "null
mbuf" panics I saw.

-- 
Grant Edwards
grante@visi.com

  parent reply	other threads:[~2000-07-10 13:03 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
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 [this message]
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=20000710200356.A3304@visi.com \
    --to=grante@visi.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=marco@sitek.it \
    /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).