[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-hotspot-runtime-dev
Subject:    RE: RFR(XS): 8194232: Container memory not properly recognized.
From:       "Lindenmaier, Goetz" <goetz.lindenmaier () sap ! com>
Date:       2017-12-27 11:24:04
Message-ID: 055a9833c3104aafa78c255478be7923 () sap ! com
[Download RAW message or body]

Hi Martin,

Yes, I also figured that the constant is one system page less than max long.
If the system pages are > 64K, this constant will be too small, again.
But I'm not sure whether adding 8 zeros is right thing to do in ramp down phase.

Best regards,
  Goetz.


> -----Original Message-----
> From: Doerr, Martin
> Sent: Mittwoch, 27. Dezember 2017 12:10
> To: Lindenmaier, Goetz <goetz.lindenmaier@sap.com>; hotspot-runtime-
> dev@openjdk.java.net
> Subject: RE: RFR(XS): 8194232: Container memory not properly recognized.
> 
> Hi Götz,
> 
> thanks for fixing it.
> 
> I wonder if 4 zeroes will be sufficient on all linux distros in the long run. Does
> anything speak against using e.g. 8 zeroes?
> 
> Best regards,
> Martin
> 
> 
> -----Original Message-----
> From: hotspot-runtime-dev [mailto:hotspot-runtime-dev-
> bounces@openjdk.java.net] On Behalf Of Lindenmaier, Goetz
> Sent: Mittwoch, 27. Dezember 2017 11:38
> To: hotspot-runtime-dev@openjdk.java.net
> Subject: RFR(XS): 8194232: Container memory not properly recognized.
> 
> Hi
> 
> Please review and sponsor this tiny fix. It needs to go to jdk10.
> http://cr.openjdk.java.net/~goetz/wr17/8194232-
> ppcle_unlimited/webrev.01/
> 
> TestAggressiveHeap.java fails because the container recognition
> misinterprets the available memory size. On SLES 12.1 ppc64le,
> GET_CONTAINER_INFO() sets memlimit to 0x7FFFFFFFFFFF0000. This
> is compared to UNLIMITED_MEM == 0x7FFFFFFFFFFFF000, making
> the VM believe memory is _not_ unlimited.
> 
> Best regards,
>   Goetz.

[prev in list] [next in list] [prev in thread] [next in thread]