9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: C H Forsyth <forsyth@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] qunlock
Date: Tue, 22 Jun 2004 10:09:19 +0100	[thread overview]
Message-ID: <29dbd0842758b89af800a214a30c9fac@vitanuova.com> (raw)
In-Reply-To: <ceee1ac56f50e184ff103c3edc5db478@vitanuova.com>

[-- Attachment #1: Type: text/plain, Size: 179 bytes --]

actually, i'd have said such an effect was unusable (or relying on it
was pointless) in general, at least with more than one process, so i'm
now more curious how you'd use it.

[-- Attachment #2: Type: message/rfc822, Size: 5134 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 109 bytes --]

i'd have thought it best to regard it as best avoided.
does it happen, or was it something you wanted to do?

[-- Attachment #2.1.2: Type: message/rfc822, Size: 2595 bytes --]

From: dvd@davidashen.net
To: 9fans@cse.psu.edu
Subject: [9fans] qunlock
Date: Tue, 22 Jun 2004 11:04:20 +0500
Message-ID: <259e5ab496f281b48d4e6ad53a58891d@davidashen.net>

calling qunlock on an unlocked QLock is no-op, isn't it?

  reply	other threads:[~2004-06-22  9:09 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 [this message]
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
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=29dbd0842758b89af800a214a30c9fac@vitanuova.com \
    --to=forsyth@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).