Quote: a monitor is a scheduler for a resource with associated data and procedures; serves only one program at a time; organizes the critical regions [»hoarCA10_1974]

Quote: a monitor manages a resource with mutual-exclusion; users simply execute allocate and release procedures [»dennPJ_1980]

Quote: a monitor consists of shared data, a mutex, and zero or more condition variables [»birrAD_1991]

Quote: a mutex protects the invariant of the associated data; restore the invariant before calling Wait or Signal [»birrAD_1991]

Quote: implement critical regions by a shared class or monitor; its operations exclude each other over time [»brinP_1973]

Quote: combine critical regions into a secretary process; invoked, as needed, by its directors; order is undefined [»dijkEW2_1971]

Quote: Modula-3's condition variables are simpler than Hoare's original design for monitors

Quote: message-passing is the major alternative to monitors [»bacoDF10_2000]

Quote: parallel processes usually don't care what happens to results; an asynchronous 'out' statement is better than a monitor call [»carrN4_1989]

Quote: V uses time servers to serialize access to resources; better than monitors since independent of client [»cherDR4_1984]

Quote: use wait and signal operations inside a monitor to wait for other resources [»hoarCA10_1974]

Quote: synchronize through monitors with explicit await queues; insures mutual exclusion of access to monitored variables [»brinP4_1999]

Quote: since a monitor locks an entire data structure, PORTAL has resources to lock individual data items; i.e., semaphores [»schiR4_1980]

Quote: for write-once fields, the commit/reconcile/fence (CRF) memory model needs monitor-like locks and a freeze op

Quote: deadline promotion -- a task with a short deadline can promote a task with a long deadline if it holds a locked monitor [»clarDD12_1995]

Quote: in PORTAL, a priority is assigned to both processes and monitors; if a process inside a monitor, it takes the monitor's priority [»schiR4_1980]

Quote: Guava avoids lock fields in object headers; only monitors require locks [»bacoDF10_2000]

Quote: Guava monitors are always synchronized; other instances are uniquely owned by a single monitor and never need synchronizing [»bacoDF10_2000]

Quote: Guava implements monitors with concurrent readers and exchange of richer data types; guarantees no data races [»bacoDF10_2000]

Quote: each process is on exactly one process queue; used for monitor locks, condition variables, and fault handlers [»johnRK3_1982]

Quote: lightweight monitor using a 32-bit lock in each object; hash tables for other data; 21x faster w/o contention, 7x faster w/ contention [»yangBS3_2005]

Quote: when writing mutex code must manage locks, decide on lock granularity, and handle deadlock; hides important safety and progress properties [»harrT10_2003]

Quote: implementations of monitors typically do not guarantee mutual exclusion; too restrictive [»bacoDF10_2000]

Quote: for short reads, simple mutex often better than a reader-writer lock [»smaaB2_2006]