A short note on implementing thread exclusiveness and address space locking
A thread can make itself exclusive by disabling execution of all other threads running in the same address space. This brute force synchronization mechanism is useful in cases otherwise requiring numerous semaphore or mutex operations or when synchronizytion has to be added to existing software. Bas...
Gespeichert in:
Veröffentlicht in: | Operating systems review 1994-07, Vol.28 (3), p.38-42 |
---|---|
1. Verfasser: | |
Format: | Artikel |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
Zusammenfassung: | A thread can make itself
exclusive
by disabling execution of all other threads running in the same address space. This brute force synchronization mechanism is useful in cases otherwise requiring numerous semaphore or mutex operations or when synchronizytion has to be added to existing software. Based on the L3 experiences, the paper describes how to implement exclusiveness by locking the relevant region of a task's address space. This optimistic method scales better than suspending and later reactivating all threads explicitly. |
---|---|
ISSN: | 0163-5980 1943-586X |
DOI: | 10.1145/182110.182114 |