public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Steve West" <steve@cyglan.com>
To: <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] FreeBSD Stack issues
Date: Tue, 31 Jul 2007 19:15:00 -0000	[thread overview]
Message-ID: <02a501c7d3a7$4f6d22a0$6500a8c0@cyglan> (raw)
In-Reply-To: <46AF7A13.7080109@mlbassoc.com>

Hello,
    We are running the i386 PC eCos build with a Intel PRO 100 nic card. 
Some of our customers report that the network stack is not responding on 
busy network segments or directley on the internet. It seems as though 
broadcasts are somehow causing a problem with the stack. We have multicast 
shut off.. We are running about 100 threads with open ports and a system 
tick of 1000/second. Our network parameters are as follows:

memory 0x200000
memory for network dynamic 8388608
mbuf memory 8388608
clusters size 16777216
max open sockets 2048
number of pending events 2048

Any ideas on how to debug this would be appritaited.

Steve 


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2007-07-31 19:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-30 11:31 [ECOS] FW: [ECOS] ECOS: Free BSD - Default gateway entry , duplicate ARP//llinfo entries - Alok Singh
2007-07-30 21:54 ` Laurie Gellatly
2007-07-31 14:39   ` Alok Singh
2007-07-31 15:08     ` Gary Thomas
2007-07-31 17:49       ` Alok Singh
2007-07-31 17:55         ` Gary Thomas
2007-07-31 17:58           ` Alok Singh
2007-07-31 18:06             ` Gary Thomas
2007-07-31 19:15               ` Steve West [this message]
2007-08-31 15:54               ` Alok Singh
2007-09-14 12:54                 ` Jürgen Lambrecht

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='02a501c7d3a7$4f6d22a0$6500a8c0@cyglan' \
    --to=steve@cyglan.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).