"Windows 95 was 30 MB" is such an ignorant, obnoxious, trite take. a triple buffered framebuffer (which you want for smooth scrolling) for my 4K display is 70 MB in *pixels alone*. Obviously a complete webpage with precomposed textures would take more.https://twitter.com/julienPauli/status/1042113172143067138 …
-
-
It didn't have the oom killer, so it had to have sensible page eviction/swapping solutions or just swap to death on overcommit
-
What are the better than OOM solution when low in memory? You could argue that OOM killer is worse than no solution, but AFAICT neither Windows nor Solaris has any solution. They just let you die while paging out, you can do that with Linux too.
-
one could argue that a better solution is to return an error from malloc/mmap/fork when a page needs to be reserved but doesn't have anything to back it.
-
I see, but I would argue that returning an error from malloc is not too different than killing the process, so I'm not sure if the extra effort really worth it for desktop applications. (should mmap do that with signal? Not entirely sure how would that work).
-
mmap can return an error too. the benefit of returning an error is that you can actually handle it, and e.g. free some caches and try again.
-
IIRC there are solutions for these usecases too: https://lwn.net/Articles/590960/ … I thought you had in mind signaling the app that accessed anonymous page w/o backing physical page. If you're unwilling to virtually allocate without physical pages, isn't that possible with Linux?
-
I'm willing to virtually allocate, I want smart ram eviction (+swap) rather than arbitrary killing.
-
Check out the link, you can get just that with Linux. And as you know, killing is not arbitrary, it can be improved, but I don't think calling heuristic people worked on "arbitrary" is constructive.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.