[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200718140811.GA1179836@rowland.harvard.edu>
Date: Sat, 18 Jul 2020 10:08:11 -0400
From: Alan Stern <stern@...land.harvard.edu>
To: Dave Chinner <david@...morbit.com>
Cc: Eric Biggers <ebiggers@...nel.org>, linux-kernel@...r.kernel.org,
linux-arch@...r.kernel.org,
"Paul E . McKenney" <paulmck@...nel.org>,
linux-fsdevel@...r.kernel.org, Akira Yokosawa <akiyks@...il.com>,
Andrea Parri <parri.andrea@...il.com>,
Boqun Feng <boqun.feng@...il.com>,
Daniel Lustig <dlustig@...dia.com>,
"Darrick J . Wong" <darrick.wong@...cle.com>,
David Howells <dhowells@...hat.com>,
Jade Alglave <j.alglave@....ac.uk>,
Luc Maranget <luc.maranget@...ia.fr>,
Nicholas Piggin <npiggin@...il.com>,
Peter Zijlstra <peterz@...radead.org>,
Will Deacon <will@...nel.org>
Subject: Re: [PATCH] tools/memory-model: document the "one-time init" pattern
> 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
Powered by blists - more mailing lists