You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow the `unified` key to be uses in a cgroups config toml file, to
directly apply resources limits using the v2 unified hierarchy, rather
than v1 -> v2 translation.
Fixes: sylabs#538
dtrudg
added a commit
to dtrudg/singularity
that referenced
this issue
Feb 1, 2022
Allow the `unified` key to be used in a cgroups config toml file, to
directly apply resource limits using the v2 unified hierarchy, rather
than v1 -> v2 translation.
Fixes: sylabs#538
Allow the `unified` key to be used in a cgroups config toml file, to
directly apply resource limits using the v2 unified hierarchy, rather
than v1 -> v2 translation.
Fixes: sylabs/singularity#538
Signed-off-by: Edita Kizinevic <[email protected]>
With #530 in place, we are now using underlying cgroups code that supports the unified key in specs-go LinuxResources.
Allow SingularityCE to accept unified cgroups resource specs, and test this functionality.
The text was updated successfully, but these errors were encountered: