Re: [PATCH 0/4] Clarify/standardize memory barriers for lock/unlock

2016-08-29 Thread Peter Zijlstra
Please use --no-chain-reply-to.

Re: [PATCH 0/4] Clarify/standardize memory barriers for lock/unlock

2016-08-29 Thread Peter Zijlstra
Please use --no-chain-reply-to.

[PATCH 0/4] Clarify/standardize memory barriers for lock/unlock

2016-08-28 Thread Manfred Spraul
Hi, as discussed before: If a high-scalability locking scheme is built with multiple spinlocks, then often additional memory barriers are required. The documentation was not as clear as possible, and memory barriers were missing / superfluous in the implementation. Patch 1: Documentation,

[PATCH 0/4] Clarify/standardize memory barriers for lock/unlock

2016-08-28 Thread Manfred Spraul
Hi, as discussed before: If a high-scalability locking scheme is built with multiple spinlocks, then often additional memory barriers are required. The documentation was not as clear as possible, and memory barriers were missing / superfluous in the implementation. Patch 1: Documentation,