From: Stephen Hemminger <shemminger@vyatta.com>
To: sclark46@earthlink.net
Cc: William Allen Simpson <william.allen.simpson@gmail.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Developers <linux-kernel@vger.kernel.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [PATCH v2] Documentation: rw_lock lessons learned
Date: Thu, 12 Nov 2009 15:00:29 -0800 [thread overview]
Message-ID: <20091112150029.1a26c641@nehalam> (raw)
In-Reply-To: <4AFC5E3F.7070609@earthlink.net>
On Thu, 12 Nov 2009 14:13:03 -0500
Stephen Clark <sclark46@earthlink.net> wrote:
> William Allen Simpson wrote:
> > In recent weeks, two different network projects erroneously
> > strayed down the rw_lock path. Update the Documentation
> > based upon comments by Eric Dumazet and Paul E. McKenney in
> > those threads.
> >
> > Merged with editorial changes by Stephen Hemminger.
> >
> > Signed-off-by: William.Allen.Simpson@gmail.com
> > Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> > ---
> > Documentation/spinlocks.txt | 186
> > ++++++++++++++++++++-----------------------
> > 1 files changed, 86 insertions(+), 100 deletions(-)
> >
>
> 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.
next prev parent reply other threads:[~2009-11-12 23:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 19:55 [PATCH resent] Documentation: rw_lock lessons learned William Allen Simpson
2009-11-10 21:22 ` Paul E. McKenney
2009-11-11 2:06 ` Stephen Hemminger
2009-11-11 17:08 ` William Allen Simpson
2009-11-11 17:37 ` Stephen Hemminger
2009-11-12 11:06 ` [PATCH v2] " William Allen Simpson
2009-11-12 15:40 ` Linus Torvalds
2009-11-12 17:04 ` Stephen Hemminger
2009-11-12 19:13 ` Stephen Clark
2009-11-12 23:00 ` Stephen Hemminger [this message]
2009-11-13 8:59 ` Stefan Richter
2009-11-13 16:15 ` William Allen Simpson
2009-12-11 17:01 ` [PATCH v2] " William Allen Simpson
2009-12-11 21:07 ` Jarek Poplawski
2009-12-12 10:36 ` William Allen Simpson
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=20091112150029.1a26c641@nehalam \
--to=shemminger@vyatta.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sclark46@earthlink.net \
--cc=torvalds@linux-foundation.org \
--cc=william.allen.simpson@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).