DOC PREVIEW
UMD CMSC 433 - Programming with Threads

This preview shows page 1-2 out of 5 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 5 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 5 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 5 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

1Programming with Threadsnotify() vs. notifyAll()• Very tricky to use notify() correctly– notifyAll() much safer• Need:– All waiters are equal– Each notify only needs to wake up 1 thread– handle InterruptedException correctlyInterruptedException• Threads t1 and t2 are waiting• Thread t3 performs a notify– thread t1 is selected• Before t1 can acquire lock, t1 is interrupted• t1’s call to wait throws InterruptedException– t1 doesn’t process notification– t2 doesn’t wake upHandling InterruptedException• synchronized (this) { while (!ready) {try {wait(); }catch (InterruptedException e) {notify();throw e;}// do whatever}Lock/Monitor Granularity• How many locks?– a single lock simplifies design– but creates a bottleneck• How long do you hold them?– Holding a lock blocks others threads– Releasing and reacquiring lock• may introduce more overhead• give wrong semantics (transaction isn’t atomic)Concurrent Queue• Need to prohibit concurrent enqueue’s• Need to prohibit concurrent dequeue’s• Can we allow a concurrent enqueue anddequeue?– Yes, most of the time2LinkedQueue [Lea 99]LinkedQueueheadlastobjectnextobjectnextobjectnext(unused)When queue is emptyLinkedQueueheadlastobjectnext(unused)LinkedQueueclass LinkedQueue { protected Node head = new Node(null); protected Node last = head; static class Node { Object object; Node next = null; Node (Object x) { object = x; } }Enqueuesynchronized void enqueue(Object x) {Node n = new Node(x);last.next = n;last = n;notifyAll();}Try to Dequeuesynchronized Object tryToDequeue() {Object x = null;Node first = head.next;if (first != null) {x = first.object;first.object = null;head = first;}return x;}Dequeuesynchronized Object dequeue() throwsInterruptedException {while (head.next == null) wait();Node first = head.next;Object x = first.object;first.object = null;head = first;return x;}3Concurrent enqueue and dequeue• Allow for concurrent enqueue and dequeue• Can’t use same monitor• If queue is full, working separate ends oflist• If queue is empty, working on same cellSeparate monitors• Have separate utility monitor objects forenqueue and dequeue• Also lock Node– If two threads need to exchange information,there needs to be a lock handoff on a commonobject• Multiple locks complicates waiting– we’ll skip waiting in this exampleLinkedQueueclass LinkedQueue { protected final Object enqueueLock = new Object(); protected final Object dequeueLock = new Object();/** Guarded by enqueueLock */ protected Node head = new Node(null);/** Guarded by dequeueLock */ protected Node last = head; static class Node { Object object; Node next = null; Node (Object x) { object = x; } }Node locking• Need to lock node n to access– n.next– n.next.objectEnqueuevoid enqueue(Object x) {Node n = new Node(x);synchronized (enqueueLock) { synchronized(last) { last.next = n;last = n;}}}Try to DequeueObject tryTodequeue() {synchronized (dequeueLock) { synchronized(head) {Object x = null;Node first = head.next;if (first != null) {x = first.object;first.object = null;head = first;} return x;}}}4Even more parallelism• Say you had many concurrent enqueue anddequeue threads• How to handle?• Assume you are willing to give up strictfirst-in, first-out ordering…Create multiple queues• Each thread either picks a queue at random• Or has a default queue, and goes to otherqueues if nothing availableWhen should you worry aboutblocking?• On a single processor system, blocking isessentially never an issue,– so long as you don’t hold any locks while youperform any operations that are• computationally expensive, or• potentially blocking (e.g., I/O)Custom locks• Can design custom locks– special features, such as trying for a lock orread locks• Built using standard locks• ReadWriteLock example– doesn’t handle recursive locksRead/Write locksclass ReadWriteLock {int readLocks = 0;boolean writeLocked = false;synchronized acquireReadLock()throws InterruptedException {while (writeLocked) wait();readLocks++;}Read/Write lockssynchronized void releaseReadLock() {readLocks--; notifyAll();}5Read/Write lockssynchronized void acquireWriteLock()throws InterruptedException {while (writeLocked || readLocks > 0) wait();writeLocked = true;}synchronized void releaseWriteLock() {writeLocked =


View Full Document

UMD CMSC 433 - Programming with Threads

Documents in this Course
Trace 1

Trace 1

62 pages

Reflection

Reflection

137 pages

Testing

Testing

25 pages

Paradigms

Paradigms

10 pages

Testing

Testing

17 pages

Java RMI

Java RMI

17 pages

Java RMI

Java RMI

17 pages

Java RMI

Java RMI

17 pages

Trace 1

Trace 1

46 pages

Jini

Jini

4 pages

Final

Final

15 pages

Java RMI

Java RMI

13 pages

Testing

Testing

16 pages

Load more
Download Programming with Threads
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Programming with Threads and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Programming with Threads 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?