From: Alexey Dobriyan <adobriyan@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Jaewon Kim <jaewon31.kim@samsung.com>,
leon@kernel.org, vbabka@suse.cz, akpm@linux-foundation.org,
labbott@redhat.com, sumit.semwal@linaro.org, minchan@kernel.org,
ngupta@vflare.org, sergey.senozhatsky.work@gmail.com,
kasong@redhat.com, bhe@redhat.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, jaewon31.kim@gmail.com,
linux-api@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: [RFC PATCH v2 1/3] meminfo_extra: introduce meminfo extra
Date: Wed, 25 Mar 2020 21:23:36 +0300 [thread overview]
Message-ID: <20200325182336.GC18706@avx2> (raw)
In-Reply-To: <20200324114645.GA2330984@kroah.com>
On Tue, Mar 24, 2020 at 12:46:45PM +0100, Greg KH wrote:
> On Tue, Mar 24, 2020 at 08:37:38PM +0900, Jaewon Kim wrote:
> > I don't know other cases in other platform.
> > Not desperately needed but I think we need one userspace knob to see overall hidden huge memory.
>
> Why? Who wants that? What would userspace do with that? And what
> exactly do you want to show?
>
> Is this just a debugging thing? Then use debugfs for that, not proc.
Yes, please use debugfs. Android can ban it in production all at once.
> Isn't that what the DRM developers are starting to do?
>
> > Additionally I'd like to see all those hidden memory in OutOfMemory log.
>
> How is anything hidden, can't you see it in the slab information?
There real usecase for something like that is vmware baloon driver.
Two VM instances oversteal pages one from another resulting in guest OOM
which looks like one giant get_free_page() memory leak from inside VM.
I don't know how often this type of issue happens nowadays but countless
OOM support tickets were filed and closed over this nonsense.
next prev parent reply other threads:[~2020-03-25 18:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200323080507epcas1p44cdb9ecb70a7a7395b3acddeda3cfd89@epcas1p4.samsung.com>
2020-03-23 8:05 ` [RFC PATCH v2 0/3] meminfo_extra: introduce meminfo extra Jaewon Kim
[not found] ` <CGME20200323080508epcas1p387c9c19b480da53be40fe5d51e76a477@epcas1p3.samsung.com>
2020-03-23 8:05 ` [RFC PATCH v2 1/3] " Jaewon Kim
2020-03-23 9:53 ` Greg KH
2020-03-24 9:11 ` Jaewon Kim
2020-03-24 10:11 ` Greg KH
2020-03-24 11:37 ` Jaewon Kim
2020-03-24 11:46 ` Greg KH
2020-03-24 12:53 ` Jaewon Kim
2020-03-24 13:19 ` Greg KH
2020-03-26 8:21 ` Jaewon Kim
2020-03-29 7:19 ` Leon Romanovsky
2020-03-29 7:23 ` Greg KH
2020-03-29 8:19 ` Leon Romanovsky
2020-03-25 18:23 ` Alexey Dobriyan [this message]
2020-03-23 12:00 ` Dave Young
[not found] ` <CGME20200323080508epcas1p2dfe6517169a65936e5ab10c4e63a19a7@epcas1p2.samsung.com>
2020-03-23 8:05 ` [RFC PATCH v2 2/3] mm: zsmalloc: include zs page size in " Jaewon Kim
[not found] ` <CGME20200323080508epcas1p3c68190cd46635b9ff026a4ae70fc7a3b@epcas1p3.samsung.com>
2020-03-23 8:05 ` [RFC PATCH v2 3/3] android: ion: include system heap " Jaewon Kim
2020-03-23 9:49 ` Greg KH
2020-03-25 18:12 ` [RFC PATCH v2 0/3] meminfo_extra: introduce " Alexey Dobriyan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200325182336.GC18706@avx2 \
--to=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jaewon31.kim@gmail.com \
--cc=jaewon31.kim@samsung.com \
--cc=kasong@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=labbott@redhat.com \
--cc=leon@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sumit.semwal@linaro.org \
--cc=vbabka@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).