From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752092AbdKMJKC convert rfc822-to-8bit (ORCPT ); Mon, 13 Nov 2017 04:10:02 -0500 Received: from mga11.intel.com ([192.55.52.93]:2457 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751377AbdKMJKA (ORCPT ); Mon, 13 Nov 2017 04:10:00 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,388,1505804400"; d="scan'208";a="2003114" From: "Reshetova, Elena" To: Peter Zijlstra CC: "linux-kernel@vger.kernel.org" , "gregkh@linuxfoundation.org" , "keescook@chromium.org" , "tglx@linutronix.de" , "mingo@redhat.com" , "ishkamiel@gmail.com" , Will Deacon , Paul McKenney , "stern@rowland.harvard.edu" , "parri.andrea@gmail.com" , "boqun.feng@gmail.com" , "dhowells@redhat.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+W86LxWH8AgAXrypCAAGnUAIAGNEwQgANK0gCAEPeXEA== Date: Mon, 13 Nov 2017 09:09:57 +0000 Message-ID: <2236FBA76BA1254E88B949DDB74E612B802BC4BA@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> In-Reply-To: <20171102135742.7o4urtltgvhr6dku@hirez.programming.kicks-ass.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-ctpclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNTNhNTA3YWMtOWRhOC00YTE2LTg4MGYtYWQ5YmM2MzcyYzVhIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjIuNS4xOCIsIlRydXN0ZWRMYWJlbEhhc2giOiI2V2ZHS3k4cDFoSzVGaUd5QU0xZkhvSzZmdDJKbThaelRwQjBpeUtaVVJZODA2Y0x4S0FkdmdwV2pKTDNLSkRHIn0= x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > 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. 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. 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.