[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AFD1FF1.7080906@s5r6.in-berlin.de>
Date: Fri, 13 Nov 2009 09:59:29 +0100
From: Stefan Richter <stefanr@...6.in-berlin.de>
To: Stephen Hemminger <shemminger@...tta.com>
CC: sclark46@...thlink.net,
William Allen Simpson <william.allen.simpson@...il.com>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel Developers <linux-kernel@...r.kernel.org>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
Eric Dumazet <eric.dumazet@...il.com>
Subject: Documentation: rw_lock lessons learned
Stephen Hemminger wrote:
> On Thu, 12 Nov 2009 14:13:03 -0500
> Stephen Clark <sclark46@...thlink.net> wrote:
>> How up to date is this doc?
>>
>> http://www.kernel.org/pub/linux/kernel/people/rusty/kernel-locking/index.html
>>
>
> Out of date.
> 1. Missing mutex's which have largely replaced semaphores.
>
> 2. Missing change to lock initialization in later kernels.
>
> 3. Missing description of lock dependency checker which should be in same guide.
4. The section on atomic reference counting should refer to <linux/kref.h>.
--
Stefan Richter
-=====-==--= =-== -==-=
http://arcgraph.de/sr/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists