You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Related to #37 and #40, we write the 32-bit MiniHeapID into _mhIndex -- for a 28 GB allocation, that is 3 MB of metadata. When large allocations like this are freed, we should MADV_FREE this metadata.
Similarly, we should be able to do something similar for the CheapHeaps we use for internal allocations.
The text was updated successfully, but these errors were encountered:
bpowers
changed the title
GlobalHeap/MeshableArena: scavenge should MADV_FREE indirection table
GlobalHeap/MeshableArena: MADV_FREE indirection table
Mar 11, 2019
bpowers
changed the title
GlobalHeap/MeshableArena: MADV_FREE indirection table
MeshableArena: MADV_FREE indirection table
Mar 11, 2019
Related to #37 and #40, we write the 32-bit
MiniHeapID
into_mhIndex
-- for a 28 GB allocation, that is 3 MB of metadata. When large allocations like this are freed, we shouldMADV_FREE
this metadata.Similarly, we should be able to do something similar for the
CheapHeap
s we use for internal allocations.The text was updated successfully, but these errors were encountered: