Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Most of my programming experience is in Windows. Can someone briefly explain why it doesn't seem to need an OOM killer? Is it happier to page? Or it always commits on allocation? Or something else.


Windows does not have fork(), which as a sibling comment indicates is one of the main issues with removing overcommit.


AFAIK windows lets whatever application asks for memory and can't get it crash, whereas the OOM killer tries to be intelligent about what gets killed.


AFAIK, Windows always commits on allocation, growing the swap file if necessary.


Why doesn't Linux do this?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: