Hello, I was rather startled recently to notice that the standard Android kernel appears to have the memory overcommit setting set to 1. This is --- as far as I can tell, the numbering got changed not long ago and not all the documentation has been updated --- these means 'allow all memory allocations even if no RAM+swap is available'.
The knock on effect of this is that running out of memory will cause either a memory trap in the application or else the OOM killer will nuke your entire process without warning. Can anyone comment on this? I know, for example, that the Android patch has modified the OOM killer. I would have thought that memory overcommit should be disabled on this kind of embedded device? -- ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ───── │ │ "They laughed at Newton. They laughed at Einstein. Of course, they │ also laughed at Bozo the Clown." --- Carl Sagan --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
