On Thu, Jun 19, 2014 at 10:03:05AM -0700, Paul E. McKenney wrote: > documentation: Add acquire/release barriers to pairing rules > > It is possible to pair acquire and release barriers with other barriers, > so this commit adds them to the list in the SMP barrier pairing section. > > Reported-by: Lai Jiangshan <la...@cn.fujitsu.com> > Signed-off-by: Paul E. McKenney <paul...@linux.vnet.ibm.com> > > diff --git a/Documentation/memory-barriers.txt > b/Documentation/memory-barriers.txt > index a6ca533a73fc..2a7c3c4fb53f 100644 > --- a/Documentation/memory-barriers.txt > +++ b/Documentation/memory-barriers.txt > @@ -757,10 +757,12 @@ SMP BARRIER PAIRING > When dealing with CPU-CPU interactions, certain types of memory barrier > should > always be paired. A lack of appropriate pairing is almost certainly an > error. > > -A write barrier should always be paired with a data dependency barrier or > read > -barrier, though a general barrier would also be viable. Similarly a read > -barrier or a data dependency barrier should always be paired with at least an > -write barrier, though, again, a general barrier is viable: > +A write barrier should always be paired with a data dependency barrier, > +acquire barrier, release barrier, or read barrier, though a general > +barrier would also be viable. Similarly a read barrier or a data > +dependency barrier should always be paired with at least a write barrier, > +an acquire barrier, or a release barrier, though, again, a general > +barrier is viable:
FWIW, Reviewed-by: Tejun Heo <t...@kernel.org> Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
