Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1320183
| From | "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] documentation: Add disclaimer |
| Date | 2016-01-28 01:50 +0100 |
| Message-ID | <qVIWC-3zl-17@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <qV92Q-2Ih-73@gated-at.bofh.it> <qV9cu-2Od-23@gated-at.bofh.it> <qV9Fw-3em-7@gated-at.bofh.it> <qVjYe-2hg-23@gated-at.bofh.it> <qVzJE-4Zj-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Jan 27, 2016 at 02:57:07PM +0000, David Howells wrote: > Peter Zijlstra <peterz@infradead.org> wrote: > > > +========== > > +DISCLAIMER > > +========== > > + > > +This document is not a specification; it is intentionally (for the sake of > > +brevity) and unintentionally (due to being human) incomplete. This document is > > +meant as a guide to using the various memory barriers provided by Linux, but > > +in case of any doubt (and there are many) please ask. > > + > > +I repeat, this document is not a specification of what Linux expects from > > +hardware. > > The purpose of this document is twofold: > > (1) to specify the minimum functionality that one can rely on for any > particular barrier, and > > (2) to provide a guide as to how to use the barriers that are available. > > Note that an architecture can provide more than the minimum requirement for > any particular barrier, but if the barrier provides less than that, it is > incorrect. > > Note also that it is possible that a barrier may be a no-op for an > architecture because the way that arch works renders an explicit barrier > unnecessary in that case. > > > + > > Can you bung an extra blank line in here if you have to redo this at all? > > > +======== > > +CONTENTS > > +======== > > > > (*) Abstract memory access model. Good point! Would you be willing to add a Signed-off-by so I can take the combined change, assuming Peter and Will are good with it? Thanx, Paul
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [v3,11/41] mips: reuse asm-generic/barrier.h Peter Zijlstra <peterz@infradead.org> - 2016-01-26 11:30 +0100
Re: [v3,11/41] mips: reuse asm-generic/barrier.h Peter Zijlstra <peterz@infradead.org> - 2016-01-26 11:40 +0100
Re: [v3,11/41] mips: reuse asm-generic/barrier.h Will Deacon <will.deacon@arm.com> - 2016-01-26 12:10 +0100
Re: [v3,11/41] mips: reuse asm-generic/barrier.h "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> - 2016-01-26 23:10 +0100
[PATCH] documentation: Add disclaimer Peter Zijlstra <peterz@infradead.org> - 2016-01-27 09:40 +0100
Re: [PATCH] documentation: Add disclaimer Will Deacon <will.deacon@arm.com> - 2016-01-27 11:20 +0100
Re: [PATCH] documentation: Add disclaimer David Howells <dhowells@redhat.com> - 2016-01-27 16:00 +0100
Re: [PATCH] documentation: Add disclaimer "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> - 2016-01-28 01:50 +0100
Re: [PATCH] documentation: Add disclaimer David Howells <dhowells@redhat.com> - 2016-01-28 21:10 +0100
Re: [v3,11/41] mips: reuse asm-generic/barrier.h "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> - 2016-01-26 23:10 +0100
csiph-web