From: "Lars Unin" <lars_unin@linuxmail.org>
To: linux-kernel@vger.kernel.org
Subject: kernel spinlocks; when to use; when appropriate?
Date: Mon, 09 Jun 2003 23:43:59 +0800 [thread overview]
Message-ID: <20030609154401.6252.qmail@linuxmail.org> (raw)
Hi,
When is is appropriate to use spinlocks in the kernel,
how are they implemented (e.g. syntax, function names) and
can anyone think of a good area of the kernel for me to look
at, that uses them?
Thanks again for any help.
Lars.
Thanks double-ly if you give code examples... :-)
--
______________________________________________
http://www.linuxmail.org/
Now with e-mail forwarding for only US$5.95/yr
Powered by Outblaze
next reply other threads:[~2003-06-09 15:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 15:43 Lars Unin [this message]
2003-06-09 15:50 ` kernel spinlocks; when to use; when appropriate? Jonathan Corbet
2003-06-10 17:57 ` LKML FAQ updating (was: Re: kernel spinlocks; when to use; when appropriate?) Rob Landley
-- strict thread matches above, loose matches on Subject: below --
2003-06-09 16:01 kernel spinlocks; when to use; when appropriate? Lars Unin
2003-06-09 17:21 ` Eli Carter
2003-06-14 16:41 Lars Unin
2003-06-15 0:50 ` Joe Korty
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=20030609154401.6252.qmail@linuxmail.org \
--to=lars_unin@linuxmail.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox