Changes between Version 9 and Version 10 of library_locks

Timestamp:

Jun 4, 2015, 1:36:24 PM (10 years ago)

Author:

laurent

Comment:

--

library_locks

@@ -13 +13 @@
 It is possible to control precisely the placement of a specific lock on a specific physical memory bank by defining a specific vseg in the application mapping. 
 
-Distributed version are available in [source:soft/giet_vm/giet_libs/sqt_user_lock.c sqt_user_lock.c] and [source:soft/giet_vm/giet_libs/sqt_user_lock.h sqt_user_lock.h] 
+Distributed version are available in [source:soft/giet_vm/giet_libs/user_sqt_lock.c user_sqt_lock.c] and [source:soft/giet_vm/giet_libs/user_sqt_lock.h user_sqt_lock.h] 
 files.
 
@@ -39 +39 @@
 
 
+The sqt_lock can be used in multi-clusters architectures, and is implemented as a - physically distributed - Synchronisation-Quad-Tree (SQT). The SQT topology is completely defined by the (x_size / y_size) parameters, with the following constraints:
+ * The involved clusters form a mesh(x_size * y_size).
+ * 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 involved clusters.
 
  === '''void sqt_lock_init'''( sqt_lock_t * lock ) ===