From: Sape Mullender <sape@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] silent limit in thread(2) Channels which can corrupt the stack?
Date: Tue, 20 Nov 2001 09:03:56 -0500 [thread overview]
Message-ID: <20011120140400.4FDC0199E4@mail.cse.psu.edu> (raw)
You are correct. It is possible to get into trouble when there are more
than 32 threads reading on a channel. I'll increase the limit and make sure
that going over the limit is flagged.
We use threaded programs very heavily here but we've never exceeded that
particular limit. One problem is that allocating (malloc/realloc) the wait list
causes incredible race conditions.
Sape
next reply other threads:[~2001-11-20 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 14:03 Sape Mullender [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-21 14:34 Fco.J.Ballesteros
2001-11-21 13:24 rog
2001-11-21 9:08 Fco.J.Ballesteros
2001-11-20 21:15 Sape Mullender
2001-11-20 20:51 David Gordon Hogan
2001-11-20 9:35 Fco.J.Ballesteros
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=20011120140400.4FDC0199E4@mail.cse.psu.edu \
--to=sape@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).