From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934990AbcCPMwF (ORCPT ); Wed, 16 Mar 2016 08:52:05 -0400 Received: from e37.co.us.ibm.com ([32.97.110.158]:58629 "EHLO e37.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933804AbcCPMwA (ORCPT ); Wed, 16 Mar 2016 08:52:00 -0400 X-IBM-Helo: d03dlp02.boulder.ibm.com X-IBM-MailFrom: paulmck@linux.vnet.ibm.com X-IBM-RcptTo: linux-kernel@vger.kernel.org Date: Wed, 16 Mar 2016 05:51:52 -0700 From: "Paul E. McKenney" To: Ingo Molnar Cc: linux-kernel@vger.kernel.org, sj38.park@gmail.com, josh@joshtriplett.org, rostedt@goodmis.org, mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com, torvalds@linux-foundation.org Subject: Re: [GIT PULL v2 rcu/next] memory-barriers.txt commits for 4.6 Message-ID: <20160316125152.GE4287@linux.vnet.ibm.com> Reply-To: paulmck@linux.vnet.ibm.com References: <20160315154631.GA1712@linux.vnet.ibm.com> <20160316072625.GA10500@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160316072625.GA10500@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 16031612-0025-0000-0000-000022C12290 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 16, 2016 at 08:26:25AM +0100, Ingo Molnar wrote: > > * Paul E. McKenney wrote: > > > [...] In fact, in view of the no-diagrams and no-quizzes restrictions, I don't > > see a way to improve on comments in the source code. [...] > > So I don't think there's such a hard restriction: AFAICS Linus's main problem was > the dual .html and .htmlx file for what essentially are the same documents. > > If you can solve that with a single (.html?) file then I think it's all OK. Very good! I do have a prototype in -rcu on branch rcu/dev that uses Linus's second suggestion, namely blanking out the answer so that the user mouse-selects it to see it. I am now chasing down the w3c validator complaints. Of course, there will likely be some review feedback. ;-) > > The memory-barriers.txt commits are available in the git repository at: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git for-mingo > > > > for you to fetch changes up to 65f95ff2e41a32dd190cf28e3abb029625eef968: > > > > documentation: Clarify compiler store-fusion example (2016-03-14 15:52:19 -0700) > > > > ---------------------------------------------------------------- > > Paul E. McKenney (7): > > documentation: Fix control dependency and identical stores > > documentation: Fix memory-barriers.txt section references > > documentation: Remove obsolete reference to RCU-protected indexes > > documentation: Subsequent writes ordered by rcu_dereference() > > documentation: Distinguish between local and global transitivity > > documentation: Add alternative release-acquire outcome > > documentation: Transitivity is not cumulativity > > > > SeongJae Park (1): > > documentation: Clarify compiler store-fusion example > > > > Documentation/memory-barriers.txt | 141 +++++++++++++++++++++++++++++++------- > > 1 file changed, 116 insertions(+), 25 deletions(-) > > Pulled into tip:locking/urgent, thanks a lot Paul! Thank you, Ingo! I will likely have one more locktorture RFC pull request, if that works for you. This fixes a bug and has very few users, so very low risk. Thanx, Paul