>>>>> "MLM" == Michael L Maraist <[EMAIL PROTECTED]> writes:
MLM> As with the relationship to the GC, my vision was that the GC MLM> would free memory objects as it found them unused (mark/sweep or MLM> what-ever), which only hands the memory regions over to the MLM> deallocator, which intelligently makes decisions about what to do MLM> with it, and how to appropriately buffer. Further, this resource MLM> management scheme provides interfaces for reclaiming memory when MLM> necessary; something obviously needed by a GC. One key aspect, MLM> however is that this provides so many features otherwise required MLM> by a GC that the GC is greatly simplified, and thus lends to MLM> greater possibilities. dan at his recent talk at boston.pm's tech meeting said he was leaning towards a copying GC scheme. this would be the split ram in half design and copy all objects to the other half at CG time. the old half is reclaimed (not even reclaimed, just ignored!) in one big chunk. maybe this could be integrated with the vmem system as well. instead of just freeing all GC objects and letting the vmem system collect and consolidate, have the GC do a copying collection so that te vmem system would have only freshly allocated chunks (at the appropriate level, hard to tell here) to manage. this is not a fully thought out idea but since vmem will consolidate and free when it can, why not have the consolidation driven by a copying GC? just musing, uri -- Uri Guttman ------ [EMAIL PROTECTED] -------- http://www.stemsystems.com -- Stem is an Open Source Network Development Toolkit and Application Suite - ----- Stem and Perl Development, Systems Architecture, Design and Coding ---- Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
