Changes between Version 8 and Version 9 of library_locks

Timestamp:

Jun 4, 2015, 1:34:05 PM (9 years ago)

Author:

laurent

Comment:

--

library_locks

@@ -12 +12 @@
 The '''user_lock_t''' being shared by several tasks, should be defined as a global variable in the application code.
 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] 
+files.
 
  == Access functions ==
@@ -31 +34 @@
 This function releases the lock. It must be called by a task after a successful lock_acquire().
  * '''lock''' : pointer on the user_lock_t structure.
+
+
+ == Distributed functions ==
+
+
+
+ === '''void sqt_lock_init'''( sqt_lock_t * lock ) ===
+This function should be called by one single task.
+ * '''lock''' : pointer on the sqt_lock_t structure.
+
+ === '''void sqt_lock_acquire'''( sqt_lock_t * lock ) ===
+This blocking function returns only when all locks of the distributed tree have been successfully taken.
+ * '''lock''' : pointer on the sqt_lock_t structure.
+
+ === '''void sqt_lock_release'''( sqt_lock_t * lock ) ===
+This function releases the lock. It must be called by a task after a successful lock_acquire().
+ * '''lock''' : pointer on the sqt_lock_t structure.
+