Changes between Version 4 and Version 5 of library_barrier

Timestamp:

Aug 4, 2014, 3:16:58 PM (10 years ago)

Author:

alain

Comment:

--

library_barrier

@@ -9 +9 @@
 == A) Simple Barrier ==
 
-The "giet_barrier_t" is a simple sense-reversing barrier. It can be safely used several times (in a loop for example),
+The ''giet_barrier_t'' is a simple sense-reversing barrier. It can be safely used several times (in a loop for example),
 but it does not scale, and should not be used when the number of expected tasks is larger than few tens.
 
@@ -22 +22 @@
 == B) Distributed Barrier == 
 
-The ''giet_sbt_barrier_t" can be used in multi-clusters architectures, and is implemented as a physically distributed Sliced-Binary-Tree (SBT).
+The ''giet_sbt_barrier_t'' can be used in multi-clusters architectures, and is implemented as a physically distributed Sliced-Binary-Tree (SBT).
 To use this distributed barrier, some placement constraints must be respected:
  * The number of tasks must be a power of 2.
@@ -35 +35 @@
 The ''barrier'' argument is a pointer on a ''giet_barrier_t'' object. The ''ntasks'' argument is the number of expected tasks.
 
-The sbt_barrier_init() contains a system call, but the sbt_barrier_wait does not.
+The sbt_barrier_init() contains a system call, but the sbt_barrier_wait() does not.
 
 '''WARNING:''' For both types of barriers, the barrier initialisation should be done by one single task.