[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150728222654.GA28456@Sligo.logfs.org>
Date: Tue, 28 Jul 2015 15:26:54 -0700
From: Jörn Engel <joern@...estorage.com>
To: David Rientjes <rientjes@...gle.com>
Cc: Mike Kravetz <mike.kravetz@...cle.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: hugetlb pages not accounted for in rss
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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists