diff options
| author | Sven Gothel <[email protected]> | 2011-09-27 11:52:53 +0200 |
|---|---|---|
| committer | Sven Gothel <[email protected]> | 2011-09-27 11:52:53 +0200 |
| commit | e4baba27507ce78e64a150ec6f69fb96f5721a34 (patch) | |
| tree | b35597020349c041eda98f2f4a82b1129874a9ca /.project | |
| parent | 73ac81eefce6b0dbf6922d2475c4b9eb9ed8a819 (diff) | |
Lock ChangeSet (fin): Cleanup, fix and enhance RecursiveLock implementation
- RecursiveLock _is_ interface.
- Use LockFactory to create a RecursiveLock.
- Impl: RecursiveLockImpl01Unfairish
- just using notify w/o any queue: fast
- still enqueuing new lock-applicants if queue full (nice)
- lock's sync extends AbstractOwnableSynchronizer and uses it (monitor)
- Impl: RecursiveLockImpl01CompleteFair
- using queue and interrupt for correctness (slow)
- lock's sync extends AbstractOwnableSynchronizer and uses it (monitor)
- Impl: RecursiveLockImplJava5 for using Java5's concurrency impl.
- to verify correctness, performance and deviation of locking time
TestRecursiveLock01 new performance measurements incl. simple avrg and deviation
shows best combined performance-deviation w/ our RecursiveLockImpl01Unfairish
os Linux and MacOSX.
RecursiveLockImpl01Unfairish is the default in LockFactory.
Adding 'private' LockDebugUtil, allowing validating all holdings locks
of one thread as stack traces (Throwable).
Besides the AbstractOwnableSynchronizer utilization, this helps debugging deadlocks
and starvation very well.
Diffstat (limited to '.project')
0 files changed, 0 insertions, 0 deletions