From 4c92a683a904729f9a0a6fc82a5d0f7ab93a7aa5 Mon Sep 17 00:00:00 2001 From: Alexey Avramov Date: Sun, 1 Sep 2019 17:55:37 +0900 Subject: [PATCH] Update readme --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index 2a96d6b..1a2dfbd 100644 --- a/README.md +++ b/README.md @@ -25,6 +25,10 @@ How can I prevent this in the future? Can't it at least keep a responsive core o — [serverfault](https://serverfault.com/questions/390623/how-do-i-prevent-linux-from-freezing-when-out-of-memory#comment417508_390625) +> "The traditional Linux OOM killer works fine in some cases, but in others it kicks in too late, resulting in the system entering a [livelock](https://en.wikipedia.org/wiki/Deadlock#Livelock) for an indeterminate period." + +— [engineering.fb.com](https://engineering.fb.com/production-engineering/oomd/) + Also look at [Why are low memory conditions handled so badly?](https://www.reddit.com/r/linux/comments/56r4xj/why_are_low_memory_conditions_handled_so_badly/) ## Solution