From: Rusty Russell <rusty@rustcorp.com.au>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
Peter Zijlstra <peterz@infradead.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [DOC PATCH] Remove mention of semaphores from kernel-locking
Date: Tue, 22 Apr 2008 02:15:30 +1000 [thread overview]
Message-ID: <200804220215.30855.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20080421145230.GX20637@parisc-linux.org>
On Tuesday 22 April 2008 00:52:30 Matthew Wilcox wrote:
> Since the consensus seems to be to eliminate semaphores where possible,
> we shouldn't be educating people about how to use them as locks.
Agreed.
> Use
> mutexes instead. Semaphores should be described in a separate document
> if we end up keeping them.
>
> Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
>
> (I'll put this patch in the semaphore git tree tomorrow unless I hear
> complaints.)
>
> diff --git a/Documentation/DocBook/kernel-locking.tmpl
> b/Documentation/DocBook/kernel-locking.tmpl index 435413c..e1f4655 100644
> --- a/Documentation/DocBook/kernel-locking.tmpl
> +++ b/Documentation/DocBook/kernel-locking.tmpl
> @@ -222,7 +222,7 @@
> <title>Three Main Types of Kernel Locks: Spinlocks, Mutexes and
> Semaphores</title>
>
> <para>
> - There are three main types of kernel locks. The fundamental type
> + There are two main types of kernel locks. The fundamental type
> is the spinlock
> (<filename class="headerfile">include/asm/spinlock.h</filename>),
> which is a very simple single-holder lock: if you can't get the
Fix title, too?
Thanks for the other fixes too; this document needs some love,
Acked,
Rusty.
next prev parent reply other threads:[~2008-04-21 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 14:52 Matthew Wilcox
2008-04-21 16:15 ` Rusty Russell [this message]
2008-04-21 16:54 ` 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=200804220215.30855.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rdunlap@xenotime.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
all inboxes | Powered by JetHome®