>EarlyOOM being a 
>userspace process that races with the memory-consuming processes and that 
>may end up not getting scheduled due to the very impending OOM condition 
>that it is trying to prevent.

earlyoom consumes 1 MiB VmRSS and all memory is locked by mlockall(). earlyoom 
works pretty fast and selects victim in 5-50 ms even with intense swapping.

>It is also unclear that it can prevent full OOM (both 
>RAM and swap completely full) 

It's clear: earlyoom forks pretty fast and well.
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 

Reply via email to