From 52950a4dffa356e249f32da89c2d81ddc539e70d Mon Sep 17 00:00:00 2001 From: kotsifa2 <kotsifa2@illinois.edu> Date: Thu, 23 Jan 2020 18:38:47 -0600 Subject: [PATCH] Dynamic instance and index description --- hpvm/docs/hpvm-specification.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hpvm/docs/hpvm-specification.md b/hpvm/docs/hpvm-specification.md index 6a1d07497a..2a1b1305a2 100644 --- a/hpvm/docs/hpvm-specification.md +++ b/hpvm/docs/hpvm-specification.md @@ -4,7 +4,7 @@ An HPVM program is a combination of host code plus a set of one or more distinct ## Dataflow Node A *dataflow node* represents unit of computation in the DFG. A node can begin execution once a data item becomes available on every one of its input edges. -A single static dataflow node represents multiple dynamic instances of the node, each executing the same computation with different index values. The dynamic instances of a node are required to be independent of each other except on HPVM synchronization operations. +A single static dataflow node represents multiple dynamic instances of the node, each executing the same computation with different index values used to uniquely identify each dynamic instance w.r.t. the others. The dynamic instances of a node may be executed concurrently, and any required synchronization must imposed using HPVM synchronization operations. Each dataflow node in a DFG can either be a *leaf node* or an *internal node*. An internal node contains a complete DFG, called a *child graph*, and the child graph itself can have internal nodes and/or leaf nodes. -- GitLab