GC papers talk a lot about nursery allocators, large object allocators, and general allocators, but they rarely say much (if anything) about managing the allocation of virtual address space usage. There are two issues here:
1. Maximizing the use of large-page mappings 2. Managing fragmentation of "holes" in the virtual address map (more of an issue for 32-bit systems). Is there prevailing wisdom on this subject? Is it something that everybody just takes for granted? Are current collectors oblivious to this? Are operating systems providing the wrong mechanisms, such that there is no point worrying about this? I'm asking because I started writing up a design note on collection, and realized that all three allocators want to sit on a virtual region manager... shap
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
