public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: AshCan@aol.com
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] How can we fix MBUF problem on old 1.3.1 code base
Date: Mon, 18 Sep 2000 17:34:00 -0000	[thread overview]
Message-ID: <85.ce8fb6.26f80e88@aol.com> (raw)

We are avoiding rebuilding the new anonymous CVS code base.  Therefore, we want to fix the existing network stack and driver code to eliminate "Out of MBUF" panics.  

We have MBUF problems both when:

1) when sending thousands of packets using multiple, concurrent ping commands.

2) When staying connected to a single socket and moving long audio data streams through the socket.

Are there are few simple fixes to the 1.3.1 code base to fix the out of MBUFs panic?  What are they?


thanks,

Dan Ash
SonicBox

             reply	other threads:[~2000-09-18 17:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-18 17:34 AshCan [this message]
2000-09-18 18:07 ` Jonathan Larmour
2000-09-19 16:11 AshCan

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=85.ce8fb6.26f80e88@aol.com \
    --to=ashcan@aol.com \
    --cc=ecos-discuss@sources.redhat.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).