18 ms·

Yeah, crash ballast is an extremely underrated tool. It also works for the OOM killer: run a daemon with a child process that holds some fixed amount of memory

Yeah, crash ballast is an extremely underrated tool. It also works for the OOM killer: run a daemon with a child process that holds some fixed amount of memory. Adjust OOM scores of everything else on the system lower than the child. If the parent’s waitpid() returns due to an OOM kill, send an alert/shutdown nonessentials/sync buffers to disk and so on.

man8alexd 3mo ago
Maybe you should skip running a useless child process and just use PSI to monitor memory pressure.
- zbentley 3mo ago
  PSI polling is also good, but there’s no substitute for knowing for sure that the OOM killer is awake and hunting.
  - man8alexd 3mo ago
    You can't know when the OOM killer is awake and hunting. The kernel doesn't know that.
    - zbentley 3mo ago
      The approach I originally described provides a useful early warning system for that condition. It’s not perfect, but has proven useful and better than nothing many times.