magistraleinformaticanetworking:spd:2016:tbblab
Differenze
Queste sono le differenze tra la revisione selezionata e la versione attuale della pagina.
| Entrambe le parti precedenti la revisioneRevisione precedente | |||
| magistraleinformaticanetworking:spd:2016:tbblab [08/05/2016 alle 22:55 (10 anni fa)] – Massimo Coppola | magistraleinformaticanetworking:spd:2016:tbblab [09/05/2016 alle 10:12 (10 anni fa)] (versione attuale) – Massimo Coppola | ||
|---|---|---|---|
| Linea 53: | Linea 53: | ||
| You can compute on points in the stream and recycle them if the computation takes too long. Use the parallel_do methods to reinsert in the loop those points that are not completed, and let those that are completed flow out of the do_loop. | You can compute on points in the stream and recycle them if the computation takes too long. Use the parallel_do methods to reinsert in the loop those points that are not completed, and let those that are completed flow out of the do_loop. | ||
| - | * Basic use of parallel do implies the grain is always 1. Design a data structure that can aggregate more points into a single parallel_do task. Minimize data copying required by the structure, | + | |
| + | | ||
| + | * examine two solutions: | ||
| + | - the new tasks are inserted from within the loop itself, requiring a specific kind of parallel_do | ||
| + | - the new tasks are generated outside of the loop; how can you manage the synchronization between the loop and the task generators in order to prevent the loop from exiting when new tasks are about to be added? | ||
| == Extensions == | == Extensions == | ||
magistraleinformaticanetworking/spd/2016/tbblab.1462748108.txt.gz · Ultima modifica: 08/05/2016 alle 22:55 (10 anni fa) da Massimo Coppola
