On Tue, Jul 28, 2015 at 03:15:17PM -0700, David Rientjes wrote: > > Starting to account hugetlb pages in rss may lead to breakage in userspace > and I would agree with your earlier suggestion that just removing any test > for rss would be appropriate. What would you propose for me then? I have 80% RAM or more in reserved hugepages. OOM-killer is not a concern, as it panics the system - the alternatives were almost universally silly and we didn't want to deal with system in unpredictable states. But knowing how much memory is used by which process is a concern. And if you only tell me about the small (and continuously shrinking) portion, I essentially fly blind. That is not a case of "may lead to breakage", it _is_ broken. Ideally we would have fixed this in 2002 when hugetlbfs was introduced. By now we might have to introduce a new field, rss_including_hugepages or whatever. Then we have to update tools like top etc. to use the new field when appropriate. No fun, but might be necessary. If we can get away with including hugepages in rss and fixing the OOM killer to be less silly, I would strongly prefer that. But I don't know how much of a mess we are already in. Jörn -- Time? What's that? Time is only worth what you do with it. -- Theo de Raadt -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>