Changes between Version 2 and Version 3 of RamLocks
- Timestamp:
- Feb 10, 2007, 3:06:22 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
RamLocks
v2 v3 1 1 = SocLib's way of handling locks = 2 2 3 Traditionnal setups implements locks through RCU (Read/copy/update) -- ie atomic -- operations. This is archieved by not releasing the bus between a read and a write operation. Most of the time with SocLib designs, we have [wiki:NoC NoC]-centric designs rather than buses therefore we can t avoid race conditions.3 Traditionnal setups implements locks through RCU (Read/copy/update) -- ie atomic -- operations. This is archieved by not releasing the bus between a read and a write operation. Most of the time with SocLib designs, we have [wiki:NoC NoC]-centric designs rather than buses therefore we can't lock bus access between operations, and can't avoid race conditions. 4 4 5 5 A new scheme is introduced in a specific ram component:
