> Userspace isn't dead

If something looks like dead it is dead. A userspace that does not respond to user actions is a dead userspace.

вс, 19 июл. 2020 г. в 17:54, John M. Harris Jr <johnmh@splentity.com>:
On Sunday, July 19, 2020 1:47:23 AM MST Alexey A. wrote:
> >Killing users' programs needlessly is not welcome
>
> Setting limits for cgroup (MemoryMax, MemorySwapMax) leads to "Killing
> users' programs needlessly": system-wide available memory may be not
> exhausted, but OOM killer will be invoked in this cgroup.

I'm sure we can all agree that only killing off the software that people
complain causes these events is better than killing off everything else just
because the system doesn't have a ton of RAM available.

> >The goal is to ensure the kernel can keep doing its job, it's
> >not going to try to figure out what you intend for userspace, as well it
> >shouldn't.
>
> The goal is to ensure the kernel can keep doing its job *and userspace*
> doing its job. I don't need a system where the kernel is alive, but
> userspace is dead.

Userspace isn't dead when a system is thrashing. Your software is still
running. If it gets killed, you're most likely going to lose your data.

--
John M. Harris, Jr.

_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@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