Content deleted Content added
Omnipaedista (talk | contribs) eponyms |
some en-dashes |
||
Line 1:
{{Unreferenced|date=December 2009}}
The '''
First, let us consider the case of a simple process graph which is a tree. A distributed computation which is tree-structured is not uncommon. Such a process graph may arise when the computation is strictly divide-and-conquer type. A node starts the computation and divides the problem in two (or more, usually a multiple of 2) roughly equal parts and distribute those parts to other processors. This process continues recursively until the problems are of sufficiently small size to solve in a single processor.
==Algorithm==
* The initiator of a computation is the root of the tree.
Line 14:
* Termination occurs when the initiator has no children and has become idle.
==
* For a tree, it is easy to detect termination. When a leaf process determines that it has terminated, it sends a signal to its parent. In general, a process waits for all its children to send signals and then it sends a signal to its parent.
* The program terminates when the root receives signals from all its children.
==
* The algorithm for a tree can be extended to acyclic directed graphs. We add an additional integer attribute [[Deficit]] to each edge.
* On an incoming edge, Deficit will denote the difference between the number of messages received and the number of signals sent in reply.
Line 25:
* Since the graph is acyclic, some nodes will have no outgoing edges and these nodes will be the first to terminate after sending enough signals to their incoming edges. After that the nodes at higher levels will terminate level by level.
==
* If cycles are allowed, the previous algorithm does not work. This is because, there may not be any node with zero outgoing edges. So, potentially there is no node which can terminate without consulting other nodes.
* The
* The tree will be directed (i.e., the channels will be directed) with the source node (which initiates the computation) as the root.
* The spanning-tree is created in the following way. A variable ''First_Edge'' is added to each node. When a node receives a message for the first time, it initializes ''First_Edge'' with the edge through which it received the message. ''First_Edge'' is never changed afterwards. Note that, the spanning tree is not unique and it depends on the order of messages in the system.
|