CSC 456 Fall 2013/7a ac: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
==References== | ==References== | ||
[http://www.cse.chalmers.se/~tsigas/papers/StudySynchronization-IPDPS13.pdf Cederman et al.] | [http://www.cse.chalmers.se/~tsigas/papers/StudySynchronization-IPDPS13.pdf Cederman et al.] | ||
[https://developer.apple.com/library/mac/documentation/cocoa/conceptual/Multithreading/ThreadSafety/ThreadSafety.html Apple Synchronization] | |||
Revision as of 15:33, 31 October 2013
Survey of Primitives for Synchronization
Assignment
7a. Survey of primitives for synchronization Section 7.3 of Solihin covers the need for synchronization at the program level. It mentions lock and unlock operations. But real programs do not usually call lock and unlock mechanisms. Instead, they use higher-level operations, such as Java’s synchronized statement, or Open MP pragmas. Consider popular languages and common OSs such as Linux, MacOS, and Windows. How would programs do synchronization in these environments?
Ideas
synchronization constucts
syncs in clr semaphores in monitors (how many langs available in?) a study of behavior of synchronization methods in commonly used languages and systems cederman et al.