From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] page fault with lock held
Date: Tue, 12 Apr 2005 18:48:18 +0100 [thread overview]
Message-ID: <63f3640e0772381f7d2463cf53679718@terzarima.net> (raw)
In-Reply-To: <b0d473d59e11b59bb5c6771f7678ad35@plan9.bell-labs.com>
data structures that must be locked over
long-running operations, and certainly those that might sleep (directly or indirectly)
or invoke i/o elsewhere, should be protected by QLock, not Lock.
next prev parent reply other threads:[~2005-04-12 17:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 17:13 Sam
2005-04-12 17:28 ` jmk
2005-04-12 17:31 ` Russ Cox
2005-04-12 17:37 ` Brantley Coile
[not found] ` <154c5e08c9c69f0f288db9ae8050a015@coraid.com>
2005-04-12 17:47 ` Russ Cox
2005-04-12 17:48 ` Charles Forsyth [this message]
2005-04-12 18:23 ` Sam
2005-04-12 20:33 ` geoff
2005-04-12 20:41 ` Dan Cross
2005-04-12 20:58 ` Russ Cox
2005-04-13 13:13 ` Dan Cross
2005-04-13 13:20 ` Brantley Coile
2005-04-13 18:48 ` Tim Newsham
2005-04-13 21:09 ` Dan Cross
2005-04-12 22:07 ` Christopher Nielsen
2005-04-12 22:57 ` Brantley Coile
2005-04-13 7:46 ` Charles Forsyth
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=63f3640e0772381f7d2463cf53679718@terzarima.net \
--to=forsyth@terzarima.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).