Keeps track of CallsToRetrieve, how many SuccessfulRetrieves, and
total WastedBytes from cached block allocations. Dumps this data in the
MapAllocatorCache::getStats() function
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Small question.
compiler-rt/lib/scudo/standalone/secondary.h | ||
---|---|---|
437 | Looks like an extra line snuck in here. Did you run clang format on this? I don't know if it would have removed this line. |
compiler-rt/lib/scudo/standalone/secondary.h | ||
---|---|---|
437 | I just re-uploaded after running clang format |
Yeah, I should have checked for a divide by zero. Unfortunately, on arm that doesn't actually crash.
compiler-rt/lib/scudo/standalone/secondary.h | ||
---|---|---|
170 | How about adding Cache before this? To make the info down below more clear | |
172 | As discussed, I think the occurrence is useful as well, how about let's do it like 64 / 128 (50%) | |
172 | I'm wondering what the value will hint us. It seems to me the accumulated value may give limited information and may be misleading. For example, does higher wasted bytes indicate bad cache strategy? Not exactly, if it always maintains good SuccessfulRetrieves, then that may have less impact. Don't get me wrong, we still want to review that value when we are tuning the cache algorithm but in terms of general stats, we may want to provide some information which are less ambiguous. Therefore, I may suggest removing the WastedBytes |
Per discussion, the *WastedBytes* will be presented in a different way which tells how many bytes are unused in secondary blocks. @frs513 will do it in a separate CL
I will merge this change
How about adding Cache before this? To make the info down below more clear