It's possible to take this metaphor of processes fighting over memory too far. I don't think in practice app writers consider themselves to have "won" if they've managed to partially crash the user's system but keep their own process running while they did it. The goal is to not invoke the capricious god OOM at all. Interesting possibility enabled by this patch: userspace OOM killer. You don't *have* to reduce memory by freeing caches -- killing other processes is quite effective too :-). And if you have a relatively integrated environment like a phone UI, you may know perfectly well from userspace that killing that java game is better than killing the windowing system, which is better than killing the gsm daemon. (Even on desktops, one knows that killing X will also automatically kill all its clients -- so one should always start by killing those clients first, because if that works, then you've managed to escape the OOM situation with strictly less damage.)
Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds