From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] silent limit in thread(2) Channels which can corrupt the stack?
Date: Wed, 21 Nov 2001 13:24:18 +0000 [thread overview]
Message-ID: <20011121131031.8A3A8199EC@mail.cse.psu.edu> (raw)
> IMHO, the limit is not bad, since it warns you of high contention on a
> channel, which could mean that you'd better split the work somehow.
you might want this... it's often useful to use channels as a
serialisation mechanism. in Limbo, i've often had potentially more
than 64 processes blocking on a channel.
i haven't had more than a brief look at the code, but what's the
reason threads blocked on a channel can't be linked together directly
rather than placed in a limited size array?
rog.
next reply other threads:[~2001-11-21 13:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-21 13:24 rog [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-21 14:34 Fco.J.Ballesteros
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 14:03 Sape Mullender
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=20011121131031.8A3A8199EC@mail.cse.psu.edu \
--to=rog@vitanuova.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).