@BruceDawson0xB Hey; regarding https://randomascii.wordpress.com/2018/08/16/24-core-cpu-and-i-cant-type-an-email-part-one/ … - Was this when Chrome was compiled with msvc? Otherwise I'm confused about how CFG was affecting V8 allocations if you were compiling with clang-cl and only using CFG on system libraries....?
Okay; yea, that makes sense. Reusing address space reduces the bitmap size; but so would enabling CFG on more things - JITted regions, libraries - fewer call targets, less bitmap usage.
-
-
But combining more CFG use with address reuse would be dangerous since prior call targets would still be valid even after you've deallocated and replaced.
-
I don't follow. This would only be dangerous if the old CFG bitmap was retained, which be an odd thing to do. Please run some tests to confirm your ideas. I don't think they match the reality. Start with these and vmmap:https://github.com/randomascii/blogstuff/tree/master/cfg …
End of conversation
New conversation -
-
-
> fewer call targets, less bitmap usage Nope. The bitmap is always there. Fewer call targets just means fewer 1s, more 0s
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.