Re: [rvm-research] Pre-Tenuring

Nursery is placed at one end of the virtual heap. And all other spaces including the mature immix to the left of nursery. All pointers from the left of nursery into the nursery are caught by the barrier. So based upon this, mutator’s immix space is a mature space, which means, the problem should not be in pointer tracking.

> On Aug 11, 2018, at 12:26 AM, Eliot Moss <[email protected]> wrote:
> 
> On 8/10/2018 5:45 PM, Shoaib Akram wrote:
>> I have 1 GC thread and 1 mutator thread. I have one immix space and 2 immix allocators. One allocator for the mutator context and one for the GC context.
>> My understanding of MMTk is that each space gets a 4 MB chunk from a global free list. Then, each allocator gets a 32 KB block from the space. Based on this understanding, communicating information b/w the mutator and the GC allocator should not be a concern. I guess that’s a fundamental tenet of MMTk design.
> 
> That sounds good - I am understanding more as we go.
> 
> The one thing I am wondering about now is whether the overall
> configuration "believes" the Mutator's immix space is a mature
> space (which would need a write barrier, etc.) or a young space.
> If it "believes" it to be a young space, things might get confused,
> maybe for a variety of reasons (trying to copy something that
> should not be copied; write barriers missed that should have
> happened; ...).
> 
> Best - EM


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Jikesrvm-researchers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jikesrvm-researchers