RFR: 8321931: memory_swap_current_in_bytes reports 0 as "unlimited" [v8]
Gerard Ziemski
gziemski at openjdk.org
Mon Jan 29 18:22:33 UTC 2024
On Sat, 27 Jan 2024 02:39:43 GMT, Gerard Ziemski <gziemski at openjdk.org> wrote:
>> We make a distinction between 0 for a limit vs non-limit cgroup values.
>>
>> For all values (limit or non-limit), 0 simply means 0.
>>
>> Output before from `jcmd PID VM.info`:
>>
>>
>> container (cgroup) information:
>> container_type: cgroupv2
>> cpu_cpuset_cpus: not supported
>> cpu_memory_nodes: not supported
>> active_processor_count: 8
>> cpu_quota: not supported
>> cpu_period: not supported
>> cpu_shares: not supported
>> memory_limit_in_bytes: unlimited
>> memory_and_swap_limit_in_bytes: unlimited
>> memory_soft_limit_in_bytes: unlimited
>> memory_usage_in_bytes: 11129120 k
>> memory_max_usage_in_bytes: not supported
>> memory_swap_current_in_bytes: unlimited
>> memory_swap_max_limit_in_bytes: unlimited
>> maximum number of tasks: 18963
>> current number of tasks: 33
>>
>>
>> Output now from `jcmd PID VM.info`:
>>
>>
>> container (cgroup) information:
>> container_type: cgroupv2
>> cpu_cpuset_cpus: not supported
>> cpu_memory_nodes: not supported
>> active_processor_count: 8
>> cpu_quota: not supported
>> cpu_period: not supported
>> cpu_shares: not supported
>> memory_limit_in_bytes: unlimited
>> memory_and_swap_limit_in_bytes: unlimited
>> memory_soft_limit_in_bytes: unlimited
>> memory_usage_in_bytes: 4962584 k
>> memory_max_usage_in_bytes: not supported
>> memory_swap_current_in_bytes: 0
>> memory_swap_max_limit_in_bytes: unlimited
>> maximum number of tasks: 18963
>> current number of tasks: 33
>>
>> In this example `memory_swap_current_in_bytes` should be printed as equal to 0, not "unlimited".
>
> Gerard Ziemski has updated the pull request incrementally with one additional commit since the last revision:
>
> jerboaa feedback
Thank you all for the reviews!
I will re-run Mach5 teir1-5 tests, just in case, before I push it...
-------------
PR Comment: https://git.openjdk.org/jdk/pull/17314#issuecomment-1915309379
More information about the hotspot-runtime-dev
mailing list