The Art of Multiprocessor Programming¶
Herlihy, M., & Shavit, N. (2008). The Art of Multiprocessor Programming. Morgan Kaufmann.
Cited by¶
2 citations across 2 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Interference and Contention
- The signature separates three structural states: (1) isolated access (no contention), (2) concurrent access to a limited resource (contention manifesting), and (3) degraded performance across all consumers, a tripartite separation Herlihy and Shavit (2008) develop in their canonical treatment of multiprocessor synchronization.
This sourceMorgan Kaufmann. Canonical multiprocessor synchronization text: develops the three-state structural separation of isolated, contending, and degraded access to shared concurrent objects.
- The signature separates three structural states: (1) isolated access (no contention), (2) concurrent access to a limited resource (contention manifesting), and (3) degraded performance across all consumers, a tripartite separation Herlihy and Shavit (2008) develop in their canonical treatment of multiprocessor synchronization.
- Race Condition
- The fix family is correspondingly compressed into a small menu: serialize the accesses (locking), make the operation atomic (compare-and-swap), Partition the state so accesses do not collide (sharding by key or jurisdiction), assign priority (queues, scheduling), or reconcile after the fact (optimistic concurrency, merge).
This sourceStandard concurrency reference for the fix menu: locking/serialization, compare-and-swap atomics, partitioning, and the trade-offs among them.
- The fix family is correspondingly compressed into a small menu: serialize the accesses (locking), make the operation atomic (compare-and-swap), Partition the state so accesses do not collide (sharding by key or jurisdiction), assign priority (queues, scheduling), or reconcile after the fact (optimistic concurrency, merge).
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. Neither this nor any other of the 2 citations of this work carries a recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:5915882d5e83 · see in the full table