Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Date:   Tue, 22 Mar 2022 03:28:12 +0000
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
Message-ID: <YjlCTOrCUHnVxIqj@casper.infradead.org>
References: <20220322032225.1402992-1-zhangyinan2019@email.szu.edu.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20220322032225.1402992-1-zhangyinan2019@email.szu.edu.cn>
Precedence: bulk

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?