From: Stephen Hemminger <shemminger@vyatta.com>
To: William Allen Simpson <william.allen.simpson@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Jarek Poplawski <jarkao2@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Linux Kernel Developers <linux-kernel@vger.kernel.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>,
Stephen Clark <sclark46@earthlink.net>,
Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: Re: [PATCH v3] Documentation: rw_lock lessons learned
Date: Mon, 14 Dec 2009 09:50:06 -0800 [thread overview]
Message-ID: <20091214095006.5cfc57a0@nehalam> (raw)
In-Reply-To: <4B254ABE.9040002@gmail.com>
On Sun, 13 Dec 2009 15:12:46 -0500
William Allen Simpson <william.allen.simpson@gmail.com> wrote:
> In recent months, 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.
>
> Further updates await somebody else with more expertise.
>
> Changes:
> - Merged with extensive content by Stephen Hemminger.
> - Fix one of the comments by Linus Torvalds.
>
> Signed-off-by: William.Allen.Simpson@gmail.com
> Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> ---
> Documentation/spinlocks.txt | 184 ++++++++++++++++++++-----------------------
> 1 files changed, 84 insertions(+), 100 deletions(-)
The whole document needs a writer to go over it and make it readable.
Something like an updated chapter on locking from LDD3 book.
John? Randy?
prev parent reply other threads:[~2009-12-14 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 20:12 [PATCH v3] Documentation: rw_lock lessons learned William Allen Simpson
2009-12-14 17:50 ` Stephen Hemminger [this message]
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=20091214095006.5cfc57a0@nehalam \
--to=shemminger@vyatta.com \
--cc=akpm@linux-foundation.org \
--cc=eric.dumazet@gmail.com \
--cc=jarkao2@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sclark46@earthlink.net \
--cc=stefanr@s5r6.in-berlin.de \
--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).