From: Venkatesh Srinivas <me@acm.jhu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] kenfs question?
Date: Sat, 6 Feb 2010 22:02:27 -0500 [thread overview]
Message-ID: <f75780241002061902n613c642ax882ecad9140117bd@mail.gmail.com> (raw)
In-Reply-To: <dd6fe68a1002061612u754bf41ic04fbcfa2c2f2b4b@mail.gmail.com>
Hi,
I guess I wasn't clear; what I was asking was why it was safe to
attempt to take a lock when splhi() at all.
On a UP, if that lock is contended and interrupts are off, you'll
lockup, no? (The timer interrupt handler will never run, reschedule
will never happen, the lock holder will never run).
-- vs
next prev parent reply other threads:[~2010-02-07 3:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-06 16:12 Venkatesh Srinivas
2010-02-06 16:16 ` erik quanstrom
2010-02-11 13:31 ` Venkatesh Srinivas
2010-02-11 14:55 ` erik quanstrom
2010-02-07 0:12 ` Russ Cox
2010-02-07 3:02 ` Venkatesh Srinivas [this message]
2010-02-07 4:44 ` erik quanstrom
2010-02-07 10:42 ` Charles Forsyth
2010-02-07 12:19 ` Venkatesh Srinivas
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=f75780241002061902n613c642ax882ecad9140117bd@mail.gmail.com \
--to=me@acm.jhu.edu \
--cc=9fans@9fans.net \
/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).