pub enum Ordering {
Relaxed,
Release,
Acquire,
AcqRel,
SeqCst,
// some variants omitted
}
Atomic memory orderings
Memory orderings limit the ways that both the compiler and CPU may reorder instructions around atomic operations. At its most restrictive, "sequentially consistent" atomics allow neither reads nor writes to be moved either before or after the atomic operation; on the other end "relaxed" atomics allow all reorderings.
Rust's memory orderings are the same as LLVM's.
For more information see the nomicon.
RelaxedNo ordering constraints, only atomic operations.
Corresponds to LLVM's Monotonic ordering.
ReleaseWhen coupled with a store, all previous writes become visible to the other threads that perform a load with Acquire ordering on the same value.
AcquireWhen coupled with a load, all subsequent loads will see data written before a store with Release ordering on the same value in other threads.
AcqRelWhen coupled with a load, uses Acquire ordering, and with a store Release ordering.
SeqCstLike AcqRel with the additional guarantee that all threads see all sequentially consistent operations in the same order.
impl Clone for Ordering
[src]
fn clone(&self) -> Ordering
[src]
Returns a copy of the value. Read more
fn clone_from(&mut self, source: &Self)
[src]
Performs copy-assignment from source. Read more
impl Copy for Ordering
[src]
impl Debug for Ordering
[src]
fn fmt(&self, __arg_0: &mut Formatter) -> Result<(), Error>
[src]
Formats the value using the given formatter. Read more
© 2010 The Rust Project Developers
Licensed under the Apache License, Version 2.0 or the MIT license, at your option.
https://doc.rust-lang.org/std/sync/atomic/enum.Ordering.html