Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   "Reshetova, Elena" <elena.reshetova@intel.com>
To:     "paulmck@linux.vnet.ibm.com" <paulmck@linux.vnet.ibm.com>
CC:     Peter Zijlstra <peterz@infradead.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
        "keescook@chromium.org" <keescook@chromium.org>,
        "tglx@linutronix.de" <tglx@linutronix.de>,
        "mingo@redhat.com" <mingo@redhat.com>,
        "ishkamiel@gmail.com" <ishkamiel@gmail.com>,
        Will Deacon <will.deacon@arm.com>,
        "stern@rowland.harvard.edu" <stern@rowland.harvard.edu>,
        "parri.andrea@gmail.com" <parri.andrea@gmail.com>,
        "boqun.feng@gmail.com" <boqun.feng@gmail.com>,
        "dhowells@redhat.com" <dhowells@redhat.com>,
        "david@fromorbit.com" <david@fromorbit.com>
Subject: RE: [PATCH] refcount: provide same memory ordering guarantees as in
 atomic_t
Thread-Topic: [PATCH] refcount: provide same memory ordering guarantees as
 in atomic_t
Thread-Index: AQHTS+92qOdaqfxtzUSi29Fjx7+W86LxWH8AgAXrypCAAGnUAIAGNEwQgANK0gCAEPeXEIAAR10AgAAsEKA=
Date:   Mon, 13 Nov 2017 16:01:11 +0000
Message-ID: <2236FBA76BA1254E88B949DDB74E612B802BC764@IRSMSX102.ger.corp.intel.com>
References: <1508756984-18980-1-git-send-email-elena.reshetova@intel.com>
 <20171023131224.GC3165@worktop.lehotels.local>
 <2236FBA76BA1254E88B949DDB74E612B802B6A2E@IRSMSX102.ger.corp.intel.com>
 <20171027135624.GY3165@worktop.lehotels.local>
 <2236FBA76BA1254E88B949DDB74E612B802B89B8@IRSMSX102.ger.corp.intel.com>
 <20171102135742.7o4urtltgvhr6dku@hirez.programming.kicks-ass.net>
 <2236FBA76BA1254E88B949DDB74E612B802BC4BA@IRSMSX102.ger.corp.intel.com>
 <20171113131926.GD3624@linux.vnet.ibm.com>
In-Reply-To: <20171113131926.GD3624@linux.vnet.ibm.com>
Accept-Language: en-US
Content-Language: en-US
dlp-product: dlpe-windows
dlp-version: 11.0.0.116
dlp-reaction: no-action
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8BIT
MIME-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


> On Mon, Nov 13, 2017 at 09:09:57AM +0000, Reshetova, Elena wrote:
> > <snip>
> >
> > > Note that there's work done on better documents and updates to this one.
> > > One document that might be good to read (I have not in fact had time to
> > > read it myself yet :-():
> > >
> > >   https://github.com/aparri/memory-
> > > model/blob/master/Documentation/explanation.txt
> >
> > I have just finished reading over this and must say that this is excellent.
> > If I would have started reading on this topic from this doc and then move
> > to other in-tree docs, including memory-barriers.txt, I would
> > have had much less issues/questions and it would be much less of a bumpy
> > read.
> 
> Glad you like it!  May we have your Acked-by?

I think my Acked-by has little value in this case since I am really a beginner in it
myself, but I would strongly suggest to Peter and others to consider inclusion 
of this doc into the tree since I do see a value in it. Again, I am not really an
important person here :)

> 
> > Is there any plan to include it into official kernel doc tree? I really think it
> > would be very helpful for others also even basically to explain the notations,
> properties
> > and language people talk about these issues and give examples.
> 
> Yes, we do plan to submit it for inclusion.

Great, I think it would help people!

Best Regards,
Elena.

> 
> 
> 		Thanx, Paul
> 
> > I will try to improve a bit the new doc I have previously sent a patch for in the
> > spirit of this reading.
> >
> >
> > Best Regards,
> > Elena.
> >


From 1583957198138408902@xxx Mon Nov 13 13:21:38 +0000 2017
X-GM-THRID: 1582046402032606032
X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread