All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Jaewon Kim <jaewon31.kim@samsung.com>
Cc: gregkh@linuxfoundation.org, 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 0/3] meminfo_extra: introduce meminfo extra
Date: Wed, 25 Mar 2020 21:12:55 +0300	[thread overview]
Message-ID: <20200325181255.GB18706@avx2> (raw)
In-Reply-To: <20200323080503.6224-1-jaewon31.kim@samsung.com>

On Mon, Mar 23, 2020 at 05:05:00PM +0900, Jaewon Kim wrote:
> /proc/meminfo or show_free_areas does not show full system wide memory
> usage status because memory stats do not track all memory allocations.
> There seems to be huge hidden memory especially on embedded system. It
> is because some HW IPs in the system use common DRAM memory instead of
> internal memory. Device drivers directly request huge pages from the
> page allocator with alloc_pages.
> 
> In Android system, most of those hidden memory seems to be vmalloc
> pages, ion system heap memory, graphics memory, and memory for DRAM
> based compressed swap storage. They may be shown in other node but it
> seems to be useful if /proc/meminfo_extra shows all those extra memory
> information. And show_mem also need to print the info in oom situation.
> 
> Fortunately vmalloc pages is already shown by commit 97105f0ab7b8
> ("mm: vmalloc: show number of vmalloc pages in /proc/meminfo"). Swap
> memory using zsmalloc can be seen through vmstat by commit 91537fee0013
> ("mm: add NR_ZSMALLOC to vmstat") but not on /proc/meminfo.
> 
> Memory usage of specific driver can be various so that showing the usage
> through upstream meminfo.c is not easy. To print the extra memory usage
> of a driver, introduce following APIs. Each driver needs to count as
> atomic_long_t.
> 
> int register_meminfo_extra(atomic_long_t *val, int shift,
> 			   const char *name);
> int unregister_meminfo_extra(atomic_long_t *val);
> 
> Currently register ION system heap allocator and zsmalloc pages.
> Additionally tested on local graphics driver.
> 
> i.e) cat /proc/meminfo_extra | tail -3
> IonSystemHeap:    242620 kB
> ZsPages:          203860 kB
> GraphicDriver:    196576 kB

In that case definitely delete ':', spaces and KB.
They only slowdown generation and parsing in userspace.
Values should be printed /proc/vmstat does it, maybe with tab instead of
space.

	foo	1234
	bar	0
	zot	111

      parent reply	other threads:[~2020-03-25 18:13 UTC|newest]

Thread overview: 21+ 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
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
2020-03-23 11:02     ` kbuild test robot
2020-03-23 12:00     ` Dave Young
2020-03-23 12:36     ` kbuild test robot
2020-03-23  8:05   ` [RFC PATCH v2 2/3] mm: zsmalloc: include zs page size in " Jaewon Kim
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   ` Alexey Dobriyan [this message]

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=20200325181255.GB18706@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.