Changes between Version 8 and Version 9 of library_barrier

Timestamp:

Jan 4, 2015, 5:18:09 PM (10 years ago)

Author:

alain

Comment:

--

library_barrier

@@ -23 +23 @@
 
 The ''giet_sbt_barrier_t'' can be used in multi-clusters architectures, and is implemented as a physically distributed Sliced-Binary-Tree (SBT).
-The SBT topology is completely defined by the number of tasks, with the following constraints:
- * The number of tasks must be a power of 2.
- * There is one task per processor.
+The SBT topology is completely defined by the number of involved clusters, with the following constraints:
+ * The number of involved clusters must be a power of 2.
  * The involved clusters form a mesh[X][Y] where (X = Y) or (X = 2*Y).
  * The lower left involved cluster is cluster(0,0).
  * All involved clusters must contain a heap[x][y] vseg declared in the mapping.
+ * The number of involved tasks in a given cluster is the same for all clusters
 
 The available functions are:
- * '''sbt_barrier_init( giet_sbt_barrier_t * barrier, unsigned int ntasks )'''
+ * '''sbt_barrier_init( giet_sbt_barrier_t * barrier, unsigned int nclusters, unsigned int ntasks )'''
  * '''sbt_barrier_wait( giet_sbt_barrier_t * barrier )''' 
 
-The ''barrier'' argument is a pointer on a ''giet_barrier_t'' object. The ''ntasks'' argument is the number of expected tasks.
+The '''barrier''' argument is a pointer on a ''giet_barrier_t'' object. 
+The '''nclusters''' argument is the number of involved clusters.
+The '''ntasks''' argument is the number of expected tasks in a single cluster.
 
 The sbt_barrier_init() contains a system call, but the sbt_barrier_wait() does not.