On Mon, Oct 12, 2015 at 05:06:36PM +0800, Boqun Feng wrote: > Understood. > > But, IMO, the position of this section is already misleading: > > (*) Implicit kernel memory barriers. > - Locking functions. > - Interrupt disabling functions. > ->- Sleep and wake-up functions.<- > - Miscellaneous functions. > > I read it as that sleep and wake-up functions provide some kernel memory > barriers which we can use *externally*(outside sleep/wakeup themselves). I think it is useful to state that the primitives handle the ordering between the waker and wakee wrt the 'blocking' state. But I've not put much thought into wording. I wanted to finish process order 'comment' patch first. -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
