Re:Non-uniform memory access meets the OOM killer
by aristidb on Saturday March 31, 2018 @07:15AM
(#16722811)
Pardon my ignorance: How did Solaris solve this?
[ Parent
| on HN ]
Re:Non-uniform memory access meets the OOM killer
by wilun on Saturday March 31, 2018 @09:05AM
(#16723135)
I just read http://unix.derkeiler.com/Newsgroups/comp.unix.solaris/2008-... and it seems that they did not solve any problem at all; they don't allow overcommit, that's all. But they do not do anything else to compensate for the disadvantages this implies (this also have advantages, but not only)
You can do that by tuning Linux to have this behavior if you like it. In a Unix system, I don't thing this is the most desirable behavior in the general case...
Re:Non-uniform memory access meets the OOM killer
by ParrotyError on Saturday March 31, 2018 @07:22AM
(#16722823)
I can't remember but I did sit in on a presentation about 15 years ago where they explained it. I lent the notes to a senior developer and never got them back.
Re:Non-uniform memory access meets the OOM killer
by RantyDave on Saturday March 31, 2018 @08:57AM
(#16723107)
It doesn't have an OOM killer. Even more remarkably a call to allocate memory can't fail, but it may not return either. When Solaris (well, SmartOS in my case) runs completely out of memory, all hell breaks loose.