On Wed, 21 Feb 2024 14:02:12 GMT, Severin Gehwolf <sgehw...@openjdk.org> wrote:
> I'm surprised that the hierarchical memory limit look-up wouldn't see it for > v1. Either way, using the traversal approach you'd see that `foo/bar` has `2 > GB`, when traversing up the hierarchy you'd see `1 GB` for `foo` and use that > as it's less than the earlier value. So would be covered by this fix? What am > I missing? It will be needlessly slower and it will not notice during execution changes of limits on other levels of the cgroup hierarchy than the initial chosen one. ------------- PR Comment: https://git.openjdk.org/jdk/pull/17198#issuecomment-1956745199