From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1586CC31E5B for ; Wed, 19 Jun 2019 15:30:36 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E081321721 for ; Wed, 19 Jun 2019 15:30:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729832AbfFSPae (ORCPT ); Wed, 19 Jun 2019 11:30:34 -0400 Received: from mx1.redhat.com ([209.132.183.28]:55368 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726009AbfFSPae (ORCPT ); Wed, 19 Jun 2019 11:30:34 -0400 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 7BC1030BB559; Wed, 19 Jun 2019 15:30:22 +0000 (UTC) Received: from llong.remote.csb (dhcp-17-85.bos.redhat.com [10.18.17.85]) by smtp.corp.redhat.com (Postfix) with ESMTP id BC5B319C79; Wed, 19 Jun 2019 15:30:16 +0000 (UTC) Subject: Re: [PATCH] mm, memcg: Add a memcg_slabinfo debugfs file To: Shakeel Butt Cc: Christoph Lameter , Pekka Enberg , David Rientjes , Joonsoo Kim , Andrew Morton , Linux MM , LKML , Michal Hocko , Roman Gushchin , Johannes Weiner , Vladimir Davydov References: <20190619144610.12520-1-longman@redhat.com> From: Waiman Long Organization: Red Hat Message-ID: <20831975-590f-ecab-53db-5d7e6b1a053f@redhat.com> Date: Wed, 19 Jun 2019 11:30:16 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.49]); Wed, 19 Jun 2019 15:30:34 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 6/19/19 11:18 AM, Shakeel Butt wrote: > On Wed, Jun 19, 2019 at 7:46 AM Waiman Long wrote: >> There are concerns about memory leaks from extensive use of memory >> cgroups as each memory cgroup creates its own set of kmem caches. There >> is a possiblity that the memcg kmem caches may remain even after the >> memory cgroup removal. Therefore, it will be useful to show how many >> memcg caches are present for each of the kmem caches. >> >> This patch introduces a new /memcg_slabinfo file which is >> somewhat similar to /proc/slabinfo in format, but lists only slabs that >> are in memcg kmem caches. Information available in /proc/slabinfo are >> not repeated in memcg_slabinfo. >> > At Google, we have an interface /proc/slabinfo_full which shows each > kmem cache (root and memcg) on a separate line i.e. no accumulation. > This interface has helped us a lot for debugging zombies and memory > leaks. The name of the memcg kmem caches include the memcg name, css > id and "dead" for offlined memcgs. I think these extra information is > much more useful for debugging. What do you think? > > Shakeel Yes, I think that can be a good idea. My only concern is that it can be very verbose. Will work on a v2 patch. Thanks, Longman