76ee9783a1
Replace pseudo-LRU approach of determining which buffer
to remove when running out of space allowed for cache
with approach which would remove the frame which is most
far away from newly added frame.
This is still a bit tricky because it's impossible to
distinguish which frame to delete in situation of:
CCCC...CC
^
it's either user wants to extend left segment of cached
frames and buffers from right segment should be removed
or he wants to join this two segments and in that case
buffers from right segment should be removed.
Would need a bit more investigation which situation
is more common in general usecase.
Additional changes:
- Cleanup some memutil files (which are familiar to cache limiter)
- Add option to make moviecache verbose. If DEBUG_MESSAGES is
defined in moviecache.c detailed logs would be printed to the
console.
- Movie caches are now named which helps reading debug messages.
|
||
|---|---|---|
| .. | ||
| intern | ||
| CMakeLists.txt | ||
| MEM_Allocator.h | ||
| MEM_CacheLimiter.h | ||
| MEM_CacheLimiterC-Api.h | ||
| MEM_NonCopyable.h | ||
| MEM_RefCounted.h | ||
| MEM_RefCountedC-Api.h | ||
| MEM_RefCountPtr.h | ||
| MEM_SmartPtr.h | ||
| SConscript | ||