All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Yinan Zhang <zhangyinan2019@email.szu.edu.cn>
Cc: akpm@linux-foundation.org, vbabka@suse.cz,
	william.kucharski@oracle.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, yejiajian2018@email.szu.edu.cn,
	hanshenghong2019@email.szu.edu.cn,
	caoyixuan2019@email.szu.edu.cn, zhaochongxi2019@email.szu.edu.cn,
	yuhongf@szu.edu.cn
Subject: Re: [PATCH 1/2] mm/page_owner.c: introduce vmalloc allocator for page_owner
Date: Tue, 22 Mar 2022 03:28:12 +0000	[thread overview]
Message-ID: <YjlCTOrCUHnVxIqj@casper.infradead.org> (raw)
In-Reply-To: <20220322032225.1402992-1-zhangyinan2019@email.szu.edu.cn>

On Tue, Mar 22, 2022 at 11:22:24AM +0800, Yinan Zhang wrote:
> An application's memory consumption is high and keeps increasing,
> then it is suspected of having memory leak. There are several
> commonly used memory allocators: slab, cma, vmalloc, etc. The memory
> leak identification can be speed up if page information allocated
> by an individual allocator are analyzed individually. This patch
> introduce vmalloc allocator for page_owner.

Why is /proc/vmallocinfo not enough?

  parent reply	other threads:[~2022-03-22  3:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22  3:22 [PATCH 1/2] mm/page_owner.c: introduce vmalloc allocator for page_owner Yinan Zhang
2022-03-22  3:22 ` [PATCH 2/2] mm/vmalloc.c: record the allocator in page_owner when __vmalloc_area_node complete mapping pages to virtual address Yinan Zhang
2022-03-22  3:28 ` Matthew Wilcox [this message]
     [not found]   ` <299aef9a-dd57-2197-f3cf-6b08c441f755@email.szu.edu.cn>
2022-03-22 15:10     ` [PATCH 1/2] mm/page_owner.c: introduce vmalloc allocator for page_owner Vlastimil Babka

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=YjlCTOrCUHnVxIqj@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=caoyixuan2019@email.szu.edu.cn \
    --cc=hanshenghong2019@email.szu.edu.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=vbabka@suse.cz \
    --cc=william.kucharski@oracle.com \
    --cc=yejiajian2018@email.szu.edu.cn \
    --cc=yuhongf@szu.edu.cn \
    --cc=zhangyinan2019@email.szu.edu.cn \
    --cc=zhaochongxi2019@email.szu.edu.cn \
    /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.