Release Consistency Models
Delay making writes visible
Goal
- reduce number of messages
- hide latency
But delay until when…?
- Eager release consistency (RC)
- do modifications at release
- delay until Q synchronizes with P
- P&Q must be data race free
- Use system primitives, no spin locks
- Then RC=SC with fewer messages
- Lazy consistency
- pull modifications at acquire, no push at release