RFR: 8256181: Remove Allocation of old generation on alternate memory devices functionality

[Thomas Stüfe]

Hi Thomas,

On Wed, Nov 11, 2020 at 4:12 PM Thomas Schatzl <thomas.schatzl at oracle.com>
wrote:

> Hi,
>
> On 11.11.20 15:06, Thomas Stüfe wrote:
> > Hi Thomas,
> >
> > I think this makes sense. Just a question, how are your thoughts about
> > JEP316? Do you consider AllocateHeapAt similarly unused?
>
> There are no plans to remove AllocateHeapAt functionality I am aware of.
> It is also much less intrusive than AllocateOldGenAt as you can see from
> this huge change, and actually works as far as I know :)
>

Yes, I am baffled by how invasive all that stuff was.

AllocateHeapAt caused a bit of complexity at the virtual memory APIs we
could do without, but we should maybe revise those APIs anyway. They are
really cracking at their seams.


> AllocateHeapAt is also an easy way to get huge pages for your heap via
> HugeTLBFS without reserving them exclusively upfront, or putting the
> entire java heap onto NVDIMMs (afaiu, but you might notice that I'm no
> real expert in this).


I see. I need to play around with this a bit more :)

>
>
Thanks,
>    Thomas
>


BTW I think it is good that we remove features if they are not maintained.

Cheers, Thomas