From: Rusty Russell <rusty@linuxcare.com.au>
To: Eli Carter <eli.carter@inet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: generic sleeping locks?
Date: Tue, 19 Dec 2000 11:06:35 +1100 [thread overview]
Message-ID: <E148AIe-0000UM-00@halfway> (raw)
In-Reply-To: Your message of "Mon, 18 Dec 2000 17:08:25 MDT." <3A3E98E9.F68BC13A@inet.com>
In message <3A3E98E9.F68BC13A@inet.com> you write:
> Alan Cox wrote:
> >
> > > Are there blocking lock primitives already defined somewhere in the
> > > kernel?
> >
> > down and up are normally appropriate for this
>
> Ungh. Forest. Trees. *sigh* Sorry for the dumb question.
> Thanks for the reply Alan. :)
>
> Ok, second part of the question: What about blocking read/write locks
> (with _interruptible variants)?
Documentation/DocBook/kernel-locking*
Rusty.
--
Hacking time.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-19 0:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-18 22:54 generic sleeping locks? Eli Carter
2000-12-18 23:01 ` Alan Cox
2000-12-18 23:08 ` Eli Carter
2000-12-19 0:06 ` Rusty Russell [this message]
2000-12-19 15:19 ` Eli Carter
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=E148AIe-0000UM-00@halfway \
--to=rusty@linuxcare.com.au \
--cc=eli.carter@inet.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.