From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Kernel question: i386 test-and-set problem
Date: Fri, 21 Jul 2000 09:15:44 -0400 [thread overview]
Message-ID: <200007211315.JAA06317@cse.psu.edu> (raw)
I would have left the lock in if I could have figured out how to do
it and fix the other problems. The main problem is that one side knows
p and the other side knows r. If I have one lock, one side is going
to have to look at something not under a lock. If I have two locks,
one in r and one in p, I can't figure out how to get them both to lock
in the same order.
next reply other threads:[~2000-07-21 13:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-21 13:15 presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-03 9:56 miller
2000-08-02 16:24 presotto
2000-08-02 15:43 jmk
2000-08-02 14:51 miller
2000-08-02 13:20 presotto
2000-08-02 8:32 miller
2000-07-31 17:26 presotto
2000-07-23 14:41 miller
2000-07-21 9:10 miller
2000-07-20 17:09 presotto
2000-07-20 13:54 miller
2000-07-20 2:03 jmk
2000-07-10 16:21 miller
2000-07-10 12:40 Russ Cox
2000-07-11 8:51 ` Jakub Jermar
2000-07-10 9:57 Jakub Jermar
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=200007211315.JAA06317@cse.psu.edu \
--to=presotto@plan9.bell-labs.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).