From: viro@parcelfarce.linux.theplanet.co.uk
To: John Richard Moser <nigelenki@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Locking scheme to block less
Date: Tue, 10 Aug 2004 01:51:36 +0100 [thread overview]
Message-ID: <20040810005136.GM12308@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <41181909.3070702@comcast.net>
On Mon, Aug 09, 2004 at 08:38:33PM -0400, John Richard Moser wrote:
> Currently, the kernel uses only spin_locks, which are similar to mutex
> locks;
Does it, really?
> If the kernel provided a read-write locking semaphore,
or if you would care to RTFS and find that it does...
next prev parent reply other threads:[~2004-08-10 0:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 0:38 Locking scheme to block less John Richard Moser
2004-08-10 0:51 ` viro [this message]
2004-08-10 3:14 ` John Richard Moser
2004-08-10 1:36 ` Rik van Riel
2004-08-10 3:20 ` John Richard Moser
2004-08-10 15:15 ` Martin J. Bligh
2004-08-11 2:08 ` Rik van Riel
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=20040810005136.GM12308@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nigelenki@comcast.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