On Tue, Jan 7, 2020 at 5:27 am, Mark Otaris <m...@net-c.com> wrote:
Try it. With a memory limit,
podman run --rm -it --memory=1G fedora bash -c 'dnf install -y
stress-ng && stress-ng --malloc 100 --memcpy 100 --mmap 100 --vm 100'
will use CPU but keep your system responsive. Without the memory limit
(this will hang your system),
podman run --rm -it fedora bash -c 'dnf install -y stress-ng &&
stress-ng --malloc 100 --memcpy 100 --mmap 100 --vm 100'
the system hangs and doesn’t recover after 15 minutes.
I don't think we can use this, though; or at least, I don't see how.
systemd allows limiting the memory accessible to a scope, but it
doesn't allow carving out memory for one particular scope that is not
to be accessible to other scopes. So I don't see a way to use these
memory limits to ensure sufficient memory remains available to critical
session processes. (Am I missing something?)
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
