Changes between Version 4 and Version 5 of library_locks

Timestamp:

Dec 2, 2014, 6:14:52 PM (10 years ago)

Author:

alain

Comment:

--

library_locks

@@ -10 +10 @@
 Each lock (giet_lock_t object) occupies a complete 64 bytes cache line to avoid false sharing.
 
- == Lock placement ==
-
 The lock being shared by several tasks, should be defined as a global variable of type '''user_lock_t''' in the application code.
-It is possible to control precisely the placement of a specific lock by defining a specific vseg in the application mapping. 
+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. 
 
  == Access functions ==