source:
doc/papers/concurrency/notes/lit-review.md@
42107b4
| Last change on this file since 42107b4 was 604e76d, checked in by , 8 years ago | |
|---|---|
|
|
| File size: 702 bytes | |
| Line | |
|---|---|
| 1 | lit review : |
| 2 | |
| 3 | Lister77 : nested monitor calls |
| 4 | - explains the problem |
| 5 | - no solution |
| 6 | - Lister : An implementation of monitors. |
| 7 | - Lister : Hierarchical monitors. |
| 8 | |
| 9 | Haddon77 : Nested monitor calls |
| 10 | - monitors should be release before acquiring a new one. |
| 11 | |
| 12 | Horst Wettstein : The problem of nested monitor calls revisited |
| 13 | - Solves nested monitor by allowing barging |
| 14 | |
| 15 | David L. Parnas : The non problem of nesied monitor calls |
| 16 | - not an actual problem in real life |
| 17 | |
| 18 | M. Joseph and VoR. Prasad : More on nested monitor call |
| 19 | - WTF... don't use monitors, use pure classes instead, whatever that is |
| 20 | |
| 21 | Joseph et al, 1978). |
| 22 | |
| 23 | Toby bloom : Evaluating Synchronization Mechanisms |
| 24 | - Methods to evaluate concurrency |
| 25 |
Note:
See TracBrowser
for help on using the repository browser.
