5.9 Atomic Execution🔗ℹ

Atomic mode evaluates a Racket expression without switching among Racket threads and with limited support for events. An atomic computation in this sense is not atomic with respect to other places, but only to other threads within a place.

Atomic mode is unsafe, because the Racket scheduler is not able to operate while execution is in atomic mode; the scheduler cannot switch threads or poll certain kinds of events, which can lead to deadlock or starvation of other threads. Beware that many operations can involve such synchronization, such as writing to an output port. Even if an output target is known to be free of synchronization, beware that values can have arbitrary printing procedures attached through prop:custom-write. Successful use of atomic mode requires a detailed knowledge of any implementation that might be reached during atomic mode to ensure that it terminates and does not involve synchronization.

Note that pairing start-atomic and end-atomic with dynamic-wind is useful only when

• the current exception handler is known to safely escape atomic mode, or else all possible escapes are through known continuation jumps or aborts (because breaks are disabled and no other exceptions are possible) that escape safely; and

• exception constructions, if any, avoid printing values in the exception message, or else the error value conversion handler is always used and known to be safe for atomic mode.

Using call-as-atomic is somewhat safer than using start-atomic and end-atomic, because call-as-atomic catches exceptions and re-raises them after exiting atomic mode, and it wraps any call to the error value conversion handler with call-as-nonatomic. The latter is safe for a particular atomic region, however, only if the region can be safely interrupted by a non-atomic exception construction.

Unlike call-as-atomic, start-atomic and end-atomic can be called from any OS thread as supported by ffi/unsafe/os-thread, although the calls have no effect outside of Racket threads. Using start-atomic in a future that is not running in a Racket thread blocks the future until it is resumed by touch in a Racket thread. Using start-atomic in a tech[#:doc reference.scrbl]{parallel thread} synchronizes with all coroutine threads in the same place, but not other parallel threads or futures.

See also the caveat that atomic mode is unsafe.

These functions are not significantly faster than start-atomic and end-atomic, so they provide no benefit in a context where breaks are disabled.

When call-as-atomic is used in the dynamic extent of call-as-atomic, then thunk is called directly as a non-tail call.

If thunk raises an exception, the exception is caught and re-raised after exiting atomic mode. Any call to the current error value conversion handler is effectively wrapped with call-as-nonatomic.

See also the caveat that atomic mode is unsafe.

When used not in the dynamic extent of a call to call-as-atomic, call-as-nonatomic raises exn:fail:contract.

Unlike start-atomic, start-uninterruptible in the CS implementation does not block a future that is running concurrently with Racket threads, and it does not cause a parallel thread to synchronize with coroutine threads. At the same time, such a future or parallel thread must not perform any action that blocks the future or requires synchronization with coroutine threads; successful use of uninterruptible mode in a future or parallel thread thus requires knowledge of Racket’s internals.

As a special case, an equal?-based mutable hash table (created by make-hash, for example) or a semaphore (created by make-semaphore) can be used an in uninterruptible mode if it is used only in uninterruptible mode, never concurrently; in the case of a semaphore, the semaphore’s internal counter must be non-zero when waiting on the semaphore. Direct use of a semaphore in uninterrupted mode would not make sense, but the special case allows uninterrupted mode to use data structures that normally rely on semaphores for locking, as long as they are used consistently that way. See also make-uninterruptible-lock.

Calls to start-uninterruptible and end-uninterruptible can be nested, and they can be mutually nested with calls to start-atomic and end-atomic in a coroutine thread. Since start-atomic is blocking for futures and requires synchronization in a parallel thread, it cannot be used in uninterruptible mode in a future or parallel thread.

Added in version 8.17.0.7 of package base.
Changed in version 8.18.0.2: Constrain the use of uninterruptable mode in futures and parallel threads.

Added in version 8.17.0.7 of package base.

An uninterruptable lock does not cooperate with coroutine thread scheduling. The uninterruptible-lock-acquire function enters uninterruptable mode immediately, before taking the lock or even waiting for it, and uninterruptible-lock-release exits uninterruptable mode only after releasing the lock. An uninterruptable lock is therefore useful only to guard predictably short actions that are reasonably considered atomic from the perspective of Racket threads.

Added in version 8.18.0.5 of package base.