b32d087dbb
Summary: Per offline discussion with siying, `MemoryAllocator` and `Cache` should be decouple. The idea is that memory allocator handles memory allocation, while cache handle cache policy. It is normal that external cache libraries pack couple the two components for better optimization. If we want to integrate with such library in the future, we can make a wrapper of the library implementing both `Cache` and `MemoryAllocator` interface. Pull Request resolved: https://github.com/facebook/rocksdb/pull/4676 Differential Revision: D13047662 Pulled By: yiwu-arbug fbshipit-source-id: cd42e246d80ab600b4de47d073f7d2db308ce6dd |
||
|---|---|---|
| .. | ||
| cache_bench.cc | ||
| cache_test.cc | ||
| clock_cache.cc | ||
| clock_cache.h | ||
| lru_cache_test.cc | ||
| lru_cache.cc | ||
| lru_cache.h | ||
| sharded_cache.cc | ||
| sharded_cache.h | ||