From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH resent] Documentation: rw_lock lessons learned Date: Wed, 11 Nov 2009 09:37:24 -0800 Message-ID: <20091111093724.4f40a48d@nehalam> References: <4AF9C540.5090403@gmail.com> <20091110180646.2e5859a8@nehalam> <4AFAEF78.4080807@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "Paul E. McKenney" , Linus Torvalds , Linux Kernel Developers , Linux Kernel Network Developers , Eric Dumazet To: William Allen Simpson Return-path: In-Reply-To: <4AFAEF78.4080807@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Wed, 11 Nov 2009 12:08:08 -0500 William Allen Simpson wrote: > Stephen Hemminger wrote: > > I would rather see the text in Documentation/spinlocks give an explaination > > as to why reader/writer locks are normally not desirable. > > > > The whole document needs work to make it a developer document, rather than > > a historical mail thread.. A good document says what should be done today, > > and does not have old junk or ask the reader to overly new context > > on old information. > > > You wish me to merge our patches? Sure, I am more concerned about document structure being readable than preserving my sloppy prose. > Or this is a second patch in a proposed series? No. But taking more input from others (maybe Randy will help he is a good editor) would get this back in shape. --