From: Jipeng H. <hua...@cs...> - 2011-07-26 13:50:48
|
Thanks, Daniel. Those places are really worth looking at and thinking about but actually they were all in my consideration. And I defined my new allocator and returned the allocator in the first few lines of pickAllocator if the RVMType's my own object type(There I didn't use RVMMethod to determine whether to return my own allocator). And I don't think MutatorContext.checkAllocator should affect my own allocator since my own allocator didn't fall into those several if checks. By the way, I forgot to mention that I put my own object type in RVM.txt(Hope that shouldn't be the reason). Thanks, Jipeng On Tue, 2011-07-26 at 09:30 +1000, Daniel Frampton wrote: > This is largely from memory, but hopefully it helps. > > I think pickAllocator is not called for each allocation, but when > compiling allocation sites (an exception being unresolved allocation > sites, which may also means the method information is null/not > available). > > MutatorContext.checkAllocator is also called during allocation and may > change the allocator (e.g., based on size). > > You can look at RuntimeEntrypoints.unresolvedScalar, and at > org.jikesrvm.mm.mminterface.MemoryManager.allocateScalar (or > allocateArray), to see more of the allocation path. > > Cheers, > Daniel. > > > On Tue, Jul 26, 2011 at 12:52 AM, Jipeng Huang > <hua...@cs...> wrote: > Hi all, > > I am doing something that may interfere with GC/MMTK, but I > always got > unexpected behaviors. In MemoryManager pickAllocator, I added > several > lines to return my own allocator based on the RVMType. Later > when some > conditions occur, I used new operation to allocate my own > object. And > there to avoid GC affecting the allocation, I defered GC. But > interestingly, I found sometimes it didn't execute > pickAllocator for > that new allocation, i.e, my own allocator sometimes wouldn't > be got and > the object in turn wouldn't be allocated into my space. I > wonder if > there're any other places that return an allocator before > allocating > space. > > Thanks, > Jipeng > > > ------------------------------------------------------------------------------ > Storage Efficiency Calculator > This modeling tool is based on patent-pending intellectual > property that > has been used successfully in hundreds of IBM storage > optimization engage- > ments, worldwide. Store less, Store more with what you own, > Move data to > the right place. Try It Now! > http://www.accelacomm.com/jaw/sfnl/114/51427378/ > _______________________________________________ > Jikesrvm-researchers mailing list > Jik...@li... > https://lists.sourceforge.net/lists/listinfo/jikesrvm-researchers > > ------------------------------------------------------------------------------ > Storage Efficiency Calculator > This modeling tool is based on patent-pending intellectual property that > has been used successfully in hundreds of IBM storage optimization engage- > ments, worldwide. Store less, Store more with what you own, Move data to > the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/ > _______________________________________________ Jikesrvm-researchers mailing list Jik...@li... https://lists.sourceforge.net/lists/listinfo/jikesrvm-researchers |