Hi Steve, > OOM killer may (and often does) affect system stability and cause > unexpected behavior.
We should have a daemon that re-stabilize the system in any case, re-launching processes killed. But, obvioulsy, that daemon has not be killed by oom_killer. >> I have create a small and easy memory mapper tool using a list of pointer. >> When you press '+' on the cmdline 1MB are malloc'ed and filled of data. >> The opposite when you press '-'. >> So you are sure that the memory can be used. >> >> I'm still searching instead a way to know how much memory can be used >> without using it. > > I suspect some combination of parameters in /proc/meminfo and > /proc/buddyinfo will give you that information. I don't think so. After startup the free memory decreases. Even if you do some free call it doesn't increase, because of VFS caching (nice for performance, not for know how much memory is really free). Maybe latest kernels are more sincer. >Due to rapidly declining price > of memory, the savings in memory may not justify the engineering cost. You are absolutely right, but to know how much memory is really free I think it is important. At least I'd like to find any memory leakage, that can make our system unstable even if with a lot of ram. > Yes, thank you for sharing your insights. nice, Raffaele _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
