1 / 7

Concurrent Programing: The LAB

Concurrent Programing: The LAB. More Resources. Sun’s Java documentation http://java.sun.com/javase/6/docs/api/ http://java.sun.com/docs/books/tutorial/essential/concurrency/ Modern Operating Systems (2nd Edition) by Andrew Tanenbaum (ISBN-10: 0130313580)

les
Télécharger la présentation

Concurrent Programing: The LAB

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Concurrent Programing: The LAB

  2. More Resources • Sun’s Java documentation • http://java.sun.com/javase/6/docs/api/ • http://java.sun.com/docs/books/tutorial/essential/concurrency/ • Modern Operating Systems (2nd Edition)by Andrew Tanenbaum (ISBN-10: 0130313580) • Operating System Concepts with Java by Abraham Silberschatz, Peter Baer Galvin, Greg Gagne (ISBN-10: 047176907X) • Concurrent Programming in Java: Design Principles and Patterns by Doug Lea (ISBN-10: 0201310090)

  3. Rules for Monitors • Always hold lock when operating on a condition var • Grab lock at beginning of function, release at end • Always test predicated state in while loop • while(condition == false) { cv.await(); } • NOT if(condition == false) {cv.await();} • while makes signal a hint • (Almost) never use sleep

  4. Java documentation from Sun • The absence of block-structured locking removes the automatic release of locks that occurs with synchronized methods and statements. In most cases, the following idiom should be used: Lock l = ...; l.lock(); try { // access the resource protected by this lock } finally { l.unlock(); }

  5. Using Locks Correctly • Java provides convenient mechanism. import java.util.concurrent.locks.ReentrantLock; aLock.lock(); try { … } finally { aLock.unlock(); } return 0;

  6. Using Locks Correctly • super calls the super-class version of the method public class RogueCoarse extends GalleryRogue{ RogueCoarse(String title, int _pauseInterval, int _maxInterval, GalleryPanel _panel, int _color) { super(title, _pauseInterval, _maxInterval, _panel, _color); lanes = _panel.getLaneLocks(); }

  7. Using Locks Correctly • static fields belong to class, not object public class RoguePurple extends GalleryRogue{ private static ReentrantLock rogueLock = new ReentrantLock(true); private static Condition blueHere = rogueLock.newCondition(); private static Condition purpleDone = rogueLock.newCondition(); private static int red_lane; }

More Related