On Wed 24-08-16 12:14:06, Marcin Jabrzyk wrote: [...] > Sorry to hijack the thread, but I've found it recently > and I guess it's the best place to present our point. > We are working at our custom OS based on Linux and we also suffered much > by /proc/<pid>/smaps file. As in Chrome we tried to improve our internal > application memory management polices (Low Memory Killer) using data > provided by smaps but we failed due to very long time needed for reading > and parsing properly the file. I was already questioning Pss and also Private_* for any memory killer purpose earlier in the thread because cumulative numbers for all mappings can be really meaningless. Especially when you do not know about which resource is shared and by whom. Maybe you can describe how you are using those cumulative numbers for your decisions and prove me wrong but I simply haven't heard any sound arguments so far. Everything was just "we know what we are doing in our environment so we know those resouces and therefore those numbers make sense to us". But with all due respect this is not a reason to add a user visible API into the kernel. -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
