From: AshCan@aol.com
To: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] How can we fix MBUF problem on old 1.3.1 code base
Date: Tue, 19 Sep 2000 16:11:00 -0000 [thread overview]
Message-ID: <df.9f19534.26f94c84@aol.com> (raw)
Jonathon,
thanks for those fixes. The out of MBUF crashes are
gone, but ofcourse I start gagging (playing network
audio) instead. I guess I need to pause playback to
let the network catch up. My code lets me push a button to close and reopen the socket and it is happy
again.
What should the proper way to handle the condition. I
can set a semaphore that my network thread tests for,
but at that point, what do I do when the semaphore is
set?
Would increasing the number of MBUFs help? It looks
like I only have 16 total.
thanks,
Dan Ash
next reply other threads:[~2000-09-19 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-19 16:11 AshCan [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-09-18 17:34 AshCan
2000-09-18 18:07 ` Jonathan Larmour
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=df.9f19534.26f94c84@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).