9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Kris Maglione <bsdaemon@comcast.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] does qlock(2) block all threads on a proc?
Date: Thu,  9 Aug 2007 20:26:38 -0400	[thread overview]
Message-ID: <20070810002638.GA12549@kris.home> (raw)
In-Reply-To: <c58b317a0708091714n4deef948g47b7f2e0cada34e0@mail.gmail.com>

On Fri, Aug 10, 2007 at 02:14:32AM +0200, david jeannot wrote:
>Does qlock block all threads on a same proc?
>I read lock(2) and thread(2) but I am not sure yet.

There are two very good ways for you to answer that question 
(lookman aside). One is to investigate the relevant libthread 
and libc code. The other is to test it yourself. Both are simple  
and quick. I don't know of a better way to learn than 
investigation.

-- 
Kris Maglione

Beware of the physician who is great at getting
out of trouble.


  reply	other threads:[~2007-08-10  0:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-10  0:14 david jeannot
2007-08-10  0:26 ` Kris Maglione [this message]
2007-08-10  1:56 ` erik quanstrom
2007-08-10 16:16 ` Francisco J Ballesteros
2007-08-10 16:30   ` erik quanstrom
2007-08-10 18:37     ` Francisco 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=20070810002638.GA12549@kris.home \
    --to=bsdaemon@comcast.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).