Robbie Harwood <rharwood@xxxxxxxxxx> writes: > Ben Cotton <bcotton@xxxxxxxxxx> writes: > >> For swap based actions, systemd-oomd will monitor the system-wide swap >> space and act when available swap falls below the configured >> threshold, starting with the cgroups with the highest swap usage to >> the least. Keeping some amount of swap (if enabled) available will >> prevent the kernel OOM killer from killing processes unpredictably and >> spending an unbounded amount of time afterwards. > > -1 from me. If the kernel behavior is a problem, fix it - don't kludge > around it in userspace. That is unlikely to happen. As far as I know, the kernel devs see the kernel oom killer as a kernel self protection measure and want it to fire as the last resort (and they are quite hesitant to touch userspace). That's the reason why there has been recently quite some development around various userspace oom killers, because it becomes more and more apparent, that the kernel is not going to fix this problem. Cheers, Dan
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
