The type of mutable atomic counters.
Moduleatomic-primops-0.8.8Haskell2010
Data.Atomics.Counter
Integer counters providing thread-safe, lock-free mutation functions.
Atomic counters are represented by a single memory location, such that built-in processor instructions are sufficient to perform fetch-and-add or compare-and-swap.
Remember, contention on such counters should still be minimized!
- 2 types
- 8 values
- Packageatomic-primops-0.8.8
- Exports10
- LanguageHaskell2010
- LicenceBSD-3-Clause
- SourceCounter.hs
Type of counters of counters and tickets
1 declarationCreating counters
1 declarationCreate a new counter initialized to the given value.
Tickets, used for compare-and-swap
2 declarationsSee the documentation for Data.Atomics for more explanation of the ticket abstraction. The same ideas apply here for counters as for general mutable locations (IORefs).
You should not depend on this type. It varies between different implementations of atomic counters.
Opaque tickets cannot be constructed, but they can be destructed into values.
Atomic memory operations
3 declarationsCompare and swap for the counter ADT. Similar behavior to casIORef, in particular, in both success and failure cases it returns a ticket that you should use for the next attempt. (That is, in the success case, it actually returns the new value that you provided as input, but in ticket form.)
Increment the counter by a given amount. Returns the value AFTER the increment (in contrast with the behavior of the underlying instruction on architectures like x86.)
Note that UNLIKE with boxed implementations of counters, where increment is based on CAS, this increment is O(1). Fetch-and-add does not require a retry loop like CAS.
An alternate version for when you don't care about the old value.
Non-atomic operations
3 declarationsEquivalent to readCounterForCAS followed by peekCTicket.
Just like the Data.Atomics CAS interface, this routine returns an opaque ticket that can be used in CAS operations. Except for the difference in return type, the semantics of this are the same as readCounter.
Make a non-atomic write to the counter. No memory-barrier.