Construct · 1 fields · 1 citations

readers-writers problem: a standalone construct

One name. One construct. A landmark on the map.

● anchor · a standalone construct Nearest construct by meaning·not indexed

A single standalone construct; nearby constructs are located against it in the Collider. Tap a field for its definition, unit, and measures.

Operating systems

a concurrency control problem in which many readers may share a resource at once while a writer needs exclusive access, with reader or writer priority variants.

In operating systems, readers-writers problem refers to a concurrency control problem in which many readers may share a resource at once while a writer needs exclusive access, with reader or writer priority variants. This meaning comes from Courtois (1971) in Communications of the ACM.[1]

Unit
Recovery means
Measured by

Run it through the Collider, or take the citations with you.

See how readers-writers problem sits against neighbouring constructs in the Collider, or export every reference on this page in one click.

Open in Collider Export BibTeX Report this entry

Nearby constructs

concurrency3 fields · 3 citationsjingle · one word, three constructs control4 fields · 5 citationsjingle · one word, four constructs resource4 fields · 6 citationsjingle · one word, four constructs

References

Courtois, P. J., Heymans, F., & Parnas, D. L. (1971). Concurrent control with “readers” and “writers”. Communications of the ACM, 14(10), 667-668. https://doi.org/10.1145/362759.362813

Cited on this page?

Confirm your construct, or correct us.

If your work is cited behind one of these entries, you know better than we do whether we captured the meaning right. Confirm it, suggest an edit, or dispute it, and your name goes on the entry as an author who has checked it, linked to your ORCID.

Claim your construct