From: Dave Hansen <haveblue@us.ibm.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: matthew@wil.cx, linux-kernel@vger.kernel.org
Subject: Re: fs/locks.c BKL removal
Date: Fri, 10 May 2002 15:13:03 -0700 [thread overview]
Message-ID: <3CDC45EF.9000506@us.ibm.com> (raw)
In-Reply-To: <3CDC4037.8040104@us.ibm.com>
As Linus pointed out, a semaphore is probably the wrong way to go.
The only things that really needs to be protected are the list
operations themselves.
> No, I really think the code should use a spinlock for the global list, and
> then on a per-lock basis something like a reference count and a blocking
> lock (which might be a semaphore).
--
Dave Hansen
haveblue@us.ibm.com
next prev parent reply other threads:[~2002-05-10 22:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 21:48 fs/locks.c BKL removal Dave Hansen
2002-05-10 22:13 ` Dave Hansen [this message]
2002-05-10 23:17 ` Andrew Morton
2002-05-11 19:48 ` Matthew Wilcox
2002-05-11 19:45 ` Matthew Wilcox
2002-05-12 1:40 ` Dave Hansen
2002-05-12 2:07 ` Matthew Wilcox
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=3CDC45EF.9000506@us.ibm.com \
--to=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
/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