Kunshan Wang
Kunshan Wang
> If tls is unused, possibly the call to the binding was removed and it becomes dead code. We can remove it. I think it may be true for `CommonPlan`....
> ... Those sound like leaking abstraction. Plans just need to produce reasonable sized work packets, and it is the scheduler that takes care of the load balancing. A plan...
> Do you have any real use case in mind? Any process that has two different VMs that use MMTk will face this problem. One example is Android ART +...
> I think a better way to think about this is what do we need to do in order to let MMTk have a dynamic heap range. Yes. That's the...
> We should be able to set heap start and heap end by using `VMLayout`: > I don't think we need an 'external VMMap' to solve it. If we set...
> > If we set the start and the end addresses of the heap, then the heap will be confined within that range. > > Yes. MMTk manages its heap,...
> Define what you mean by 'external vmmap/mapper'. > > If you meant that the binding should implement the proposed `ExternalChunkResource` which mmaps memory for MMTk, I don't agree with...
I would make an even stronger argument. Fixed address ranges will simply not (always) work. When a program starts, the first thing that manages the memory is the system linker/loader....
> This is an extremely confusing way to phrase it imo. All you are trying to say is we need to make MMTk more tolerant to `mmap` failures which is...
As @steveblackburn suggested, there is another option between (2) and (3). Option 2.5: Configurable heap size. The binding specifies a max heap size (not range). When initializing MMTk, it figures...