From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Stern Subject: Re: [PATCH] tools/memory-model: document the "one-time init" pattern Date: Sat, 18 Jul 2020 10:08:11 -0400 Message-ID: <20200718140811.GA1179836@rowland.harvard.edu> References: <20200717044427.68747-1-ebiggers@kernel.org> <20200718014204.GN5369@dread.disaster.area> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20200718014204.GN5369@dread.disaster.area> Sender: linux-fsdevel-owner@vger.kernel.org To: Dave Chinner Cc: Eric Biggers , linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, "Paul E . McKenney" , linux-fsdevel@vger.kernel.org, Akira Yokosawa , Andrea Parri , Boqun Feng , Daniel Lustig , "Darrick J . Wong" , David Howells , Jade Alglave , Luc Maranget , Nicholas Piggin , Peter Zijlstra , Will Deacon List-Id: linux-arch.vger.kernel.org > This is one of the reasons that the LKMM documetnation is so damn > difficult to read and understand: just understanding the vocabulary > it uses requires a huge learning curve, and it's not defined > anywhere. Understanding the syntax of examples requires a huge > learning curve, because it's not defined anywhere. Have you seen tools/memory-model/Documentation/explanation.txt? That file was specifically written for non-experts to help them overcome the learning curve. It tries to define the vocabulary as terms are introduced and to avoid using obscure syntax. If you think it needs improvement and can give some specific details about where it falls short, I would like to hear them. Alan Stern From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from netrider.rowland.org ([192.131.102.5]:51729 "HELO netrider.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1727772AbgGROIN (ORCPT ); Sat, 18 Jul 2020 10:08:13 -0400 Date: Sat, 18 Jul 2020 10:08:11 -0400 From: Alan Stern Subject: Re: [PATCH] tools/memory-model: document the "one-time init" pattern Message-ID: <20200718140811.GA1179836@rowland.harvard.edu> References: <20200717044427.68747-1-ebiggers@kernel.org> <20200718014204.GN5369@dread.disaster.area> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200718014204.GN5369@dread.disaster.area> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Dave Chinner Cc: Eric Biggers , linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, "Paul E . McKenney" , linux-fsdevel@vger.kernel.org, Akira Yokosawa , Andrea Parri , Boqun Feng , Daniel Lustig , "Darrick J . Wong" , David Howells , Jade Alglave , Luc Maranget , Nicholas Piggin , Peter Zijlstra , Will Deacon Message-ID: <20200718140811.KziOhZQbv91y287HbxsYyehRvUO8aEwCCy4AEP7o70c@z> > This is one of the reasons that the LKMM documetnation is so damn > difficult to read and understand: just understanding the vocabulary > it uses requires a huge learning curve, and it's not defined > anywhere. Understanding the syntax of examples requires a huge > learning curve, because it's not defined anywhere. Have you seen tools/memory-model/Documentation/explanation.txt? That file was specifically written for non-experts to help them overcome the learning curve. It tries to define the vocabulary as terms are introduced and to avoid using obscure syntax. If you think it needs improvement and can give some specific details about where it falls short, I would like to hear them. Alan Stern