Changes between Version 8 and Version 9 of library_locks
- Timestamp:
- Jun 4, 2015, 1:34:05 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
library_locks
v8 v9 12 12 The '''user_lock_t''' being shared by several tasks, should be defined as a global variable in the application code. 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. 14 15 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] 16 files. 14 17 15 18 == Access functions == … … 31 34 This function releases the lock. It must be called by a task after a successful lock_acquire(). 32 35 * '''lock''' : pointer on the user_lock_t structure. 36 37 38 == Distributed functions == 39 40 41 42 === '''void sqt_lock_init'''( sqt_lock_t * lock ) === 43 This function should be called by one single task. 44 * '''lock''' : pointer on the sqt_lock_t structure. 45 46 === '''void sqt_lock_acquire'''( sqt_lock_t * lock ) === 47 This blocking function returns only when all locks of the distributed tree have been successfully taken. 48 * '''lock''' : pointer on the sqt_lock_t structure. 49 50 === '''void sqt_lock_release'''( sqt_lock_t * lock ) === 51 This function releases the lock. It must be called by a task after a successful lock_acquire(). 52 * '''lock''' : pointer on the sqt_lock_t structure. 53