pkhuong / kismet-cache Goto Github PK

When a program knows it's keeping a file alive (e.g., it has an mmap-ed view of that file in memory), it doesn't make sense to evict it. We should be able to mark them as pinned, and let the replacement strategy do something useful (e.g., move them to the back of the list instead of deleting them), while attempting to obey the cache capacity.

Open question: do we want to do this purely in-memory, or shall we use (shared) file locks to denote pins?

The current implementation evicts to make sure the number of cached files is below the cache directory's capacity in files. That's good enough to be useful, but it would make sense to have the option to enforce a capacity in bytes.