I think this would be a really big improvement for workstation and other desktop spins,
the handling of out of memory situations have been a consistent paint point on Linux.
However, may I ask why EarlyOOM was chosen over something like NoHang ? I am a bit
concerned that EarlyOOM's heuristics may be too coarse, as it does not take into
account the newly-added PSI metrics  that other projects like NoHang, oomd, and
low-memory-monitor utilize. For example, if the system is thrashing, but swap is not
full, to my knowledge EarlyOOM will not see a problem, however it would be visible via
To be clear, I'd rather have something in time for 32 to improve OOM handling than
wait several release cycles for the ideal solution to be ready. I'm simply curious
about what problems, if any, were encountered with the other potential candidates.