From: dvd@davidashen.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] qunlock
Date: Thu, 24 Jun 2004 16:02:16 +0500 [thread overview]
Message-ID: <e207e6e2919e77c62863069a80f63e21@davidashen.net> (raw)
In-Reply-To: <ab397ad4f84f44cfed5f8242258a5e3b@plan9.escet.urjc.es>
>> /* canqlock(b); */
>> qunlock(b);
>
> This is very weird for me.
> Can't you rework your scheme to avoid such things?
> Perhaps this code is suggesting that your locking
> conventions may need more work.
That's why I am asking. What exactly is weird? The code actually works
in SPIN (as a model), and in Python (but I check locked() before unlocking).
The purpose is to have multiple producers and consumers on an queue
with exclusive access, with priority always given to consumers if there
are waiting ones and the queue is not empty.
The implementation of qlock/qunlock allows to unlock when not locked;
I am asking whether it is by design or by a coincidence?
David
next prev parent reply other threads:[~2004-06-24 11:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 6:04 dvd
2004-06-22 8:06 ` C H Forsyth
2004-06-22 9:09 ` C H Forsyth
2004-06-22 14:19 ` ron minnich
2004-06-22 14:38 ` boyd, rounin
2004-06-22 15:13 ` Rob Pike
2004-06-23 20:11 ` dvd
2004-06-23 20:24 ` Rob Pike
2004-06-23 21:00 ` dvd
2004-06-23 21:12 ` boyd, rounin
2004-06-24 7:19 ` Fco. J. Ballesteros
2004-06-24 10:58 ` dvd
2004-06-24 7:34 ` Fco. J. Ballesteros
2004-06-24 11:02 ` dvd [this message]
2004-06-24 11:14 ` Fco. J. Ballesteros
2004-06-24 12:18 ` dvd
2004-06-24 13:09 ` Fco. J. Ballesteros
2004-06-24 13:30 ` Sape Mullender
2004-06-24 13:47 ` boyd, rounin
2004-06-24 13:42 ` boyd, rounin
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=e207e6e2919e77c62863069a80f63e21@davidashen.net \
--to=dvd@davidashen.net \
--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).