On Tue, 02 Dec 2014 14:36:34 -0800 Thiago Macieira <thiago.macie...@intel.com> said:
> 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. we also need events from the kernel. a kernel event saying "help - we are low on memory - please do something now!". otherwise this daemon is left to have to poll and polling is not pretty on power and means the best response time of a "memory shortage" is dependent on polling interval.. and this is an eternal fight between power usage and response. events please. :) -- Carsten Haitzler (The Rasterman) <ti...@rasterman.com> _______________________________________________ Dev mailing list Dev@lists.tizen.org https://lists.tizen.org/listinfo/dev
