Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
os/bluestore: use Best-Effort policy when evicting onode from cache #12876
So, my concern here, and the reason it does what it does, is that I was worried about a situation where we have lots of onodes that still have refs and trim ends up iterating over N pinned entries each time it is called.
Perhaps we can add in a second threshold so that we only iterate over a limited number of pinned entries before giving up so that we don't spend too much CPU time? bluestore_cache_trim_max_skip_pinned or something along those lines?