On Mon, Apr 17, 2017 at 07:11:37AM +0900, Akira Yokosawa wrote: > >From 6efc224d8e6d2b64bf7a86b52d03de01ccea7032 Mon Sep 17 00:00:00 2001 > From: Akira Yokosawa <akiyks@xxxxxxxxx> > Date: Mon, 17 Apr 2017 06:53:11 +0900 > Subject: [PATCH 00/14] advsync: Use pseudo asm in code sequence > > Hi Paul, > > This series substitutes pseudo-asm codes for C style statements > in code sequences in 'Memory Barrier' section. > > Other than the substitution, Patch 2 replaces ACCESS_ONCE(), > Patch 4 is a backport of the changes made in memory-barriers.txt, > Patches 8 and 12 add footnotes to imply the necessity of data > dependency barrier, and Patch 11 renames Section "Guarantee" > to "Minimal Guarantee". > > My guess is that the original intention of the "Guarantee" > section was to present minimal guarantees free of memory barriers. > When the necessity of read dependency barrier was recognized, > the barrier sneaked into this section. > > In LaTeX, as footnotes can prevent readers' misunderstanding, > We can preserve the original intention. > > Thoughts? Good changes, queued, thank you! Of course, please feel free to submit clarifying and style patches against memory-barriers.txt if needed. Thanx, Paul > Thanks Akira > -- > Akira Yokosawa (14): > advsync: Use pseudo asm in sequence in 'Paring' section > advsync: Substitute READ_ONCE()/WRITE_ONCE() for ACCESS_ONCE() > advsync: Use pseudo asm in sequence in 'Review of Locking Impl' > advsync: Backport upstream commits regarding reordering example > advsync: Use pseudo asm in reordering example > advsync: Use pseudo asm in another reordering example > advsync: Avoid indent after minipages > advsync: Add footnote to imply necessity of data dependency barrier > advsync: Use READ_ONCE()/WRITE_ONCE() in sequence of 'Device > Operations' > advsync: Use READ_ONCE()/WRITE_ONCE() in sequence in 'Guarantees' > advsync: Rename Section 'Guarantee' to 'Minimal Guarantee' > advsync: Add another footnote implying data dependency barrier > advsync: Use pseudo asm in sequence in 'Data Dependency Barriers' > advsync: Use pseudo asm in sequence in 'SMP Barrier Pairing' > > advsync/memorybarriers.tex | 321 ++++++++++++++++++++++++--------------------- > 1 file changed, 172 insertions(+), 149 deletions(-) > > -- > 2.7.4 > -- To unsubscribe from this list: send the line "unsubscribe perfbook" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
