并行编程设计模式 Parallel Programming Patterns.ppt

* Script We have seen ways to distribute the work from the boss to the worker What about task completion – how does the boss let the workers know that the job is done and that they can go to sleep or be terminated. If we are using the rendezvous variant, then one of the tasks will be set up as a termination task also called a poison pill for each worker. So when the worker rendezvous with the boss and gets its new task – it checks the ID and sees that it is a termination task and so it goes to sleep ir terminates. In the case of the bag of tasks, once you have loaded all the tasks that need to be done then we decide that maybe the empty bag signals final task completion. So when workers empty the bag then this signals ob is done. But what if the Boss has just fallen behind in filling up the bag – what do you do then? You can use a termination task similar to what was described above- this requires that the container be more of a first in first out queue so that the termination tasks are the last entries in the queue. Boss puts in a number of termination tasks equal to the number of threads. Each worker receives a single termination task and goes of to sleep or terminate In the case of the Shared Monotonic Counter There should be a read only shared variable that indicates the Max task number All threads can access this number and determine if the counter value they pulled down exceeds the Max task – if it does then it goes to sleep or terminates * Script Here is a case study for Implementation of some Boss Code – in this case – specifically it will e a rendezvous Two threads have to synchronize and meet at some point within their execution. Once they’ve done that – there is a transfer of data Here we are looking at the Boss code: Here we have a BWlock – a BossWorker lock The Boss locks the lock Increments num_waiting – the lock is only here to protect this num_waiting variable Then the Boss checks to see the value of num_waiting If it is not equal to 2