On Tuesday 02 December 2014 18:13:51 Dominig ar Foll wrote: > Thiago, > > the kernel has indeed a defence mechanism but when it triggered the > device is already useless and furthermore the kernel will not restart > anything. > The only service available is a protection of the kernel. > That is OK when a smart human is on command, but on an embedded system, > it rarely provide anything good :-(
Understood, but please note that userspace often does not have enough information to make the correct decision about memory usage. Processes share a lot of pages by way of libraries they share, memory-mapped files, etc. and also by tricks like the launcher daemon. The only way for userspace to get the information is via /proc/*/smaps and that is not sufficient. For this daemon to work, we should really get a kernel feature. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
