RFR(M): 8171181: Supporting heap allocation on alternative memory devices

Kharbas, Kishor kishor.kharbas at intel.com
Mon Mar 6 21:21:52 UTC 2017


Hi Jini!

Yes that's right, the coredump_filter needs to modified to dump file-backed shared mappings.

Thanks for pointing this out!

Kishor

> -----Original Message-----
> From: Jini George [mailto:jini.george at oracle.com]
> Sent: Saturday, March 4, 2017 1:01 AM
> To: Kharbas, Kishor <kishor.kharbas at intel.com>; hotspot-runtime-
> dev at openjdk.java.net
> Subject: Re: RFR(M): 8171181: Supporting heap allocation on alternative
> memory devices
> 
> Hi Kishor,
> 
> Wanted a clarification. For Linux, wouldn't the coredump_filter file also have
> to be modified (by setting bit 3 or bit 8 ?) to ensure that the java heap gets
> dumped into the corefile when a coredump occurs ?
> 
> Thanks,
> Jini.
> 
> On 2/28/2017 5:22 AM, Kharbas, Kishor wrote:
> > Hello all!I have proposed a JEP to support allocation of Java heap on
> > new memory devices such as NV-DIMMs like Intel's 3D XPoint. Such a
> > feature has applications in multi-JVM deployments, big data
> > applications and in-memory databases. Please find the details here -
> > https://bugs.openjdk.java.net/browse/JDK-8171181 and the patch for the
> > implementation is at
> > http://cr.openjdk.java.net/~kkharbas/8153327_webrev.04 I would
> > appreciate a review and feedback from the community for this JEP.
> > Thank you! Kishor



More information about the hotspot-runtime-dev mailing list