Received: by 2002:a05:6a10:8a4f:0:0:0:0 with SMTP id dn15csp2600471pxb; Mon, 31 Jan 2022 03:40:28 -0800 (PST) X-Google-Smtp-Source: ABdhPJxXRU2sV7Z3k5MIZL0ADey4kgkPr/6MfP8pIH2geW5jweHBZnntJIVx33kKNCJAyd+CIa0X X-Received: by 2002:a63:e704:: with SMTP id b4mr16336884pgi.315.1643629228357; Mon, 31 Jan 2022 03:40:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643629228; cv=none; d=google.com; s=arc-20160816; b=qErpYXWe05t07xCBHGX8cN1ILSNihU/0oM1Yn0ZAaYVxjGPhCoh0SltQiPA+ohAyAo +6e5Z9UHsBHq3ONcpfBrO1OWlxuzUL3aENqC6V9VB+Y2HzDJ1GAS9G3EronU8u1KvwLV dFDxM+EKIem59ito4lTZEI/sLmso9F9Y3mGaQpn2ZQTtAh8sMeJOFwHtkBWEo4/TXMai 6zldT+BSF++bh4BhhNoLXfFrwSvdiVZ9RfWfpycFm4YOAY/KA5tTolKsAlbF/IuvE8hK PC/U0TooIgeWAXeHxGfiKshLAKxnneOMFPBpOtRBccpaGurc8ZjCNSgUcDyeASD9MPuL rwyw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=cPaaPTwaHnrZy5BBxHC8AwDN/oX7cxF5Nc5fiuL/xAs=; b=beacUlUG1GSFFgenLhuvWCy2V4Dz4hRZmVZEB+xtFvxVTBm46m1H9iFNFZBxUde2UI O5OsT9xTukaCGMkeYDj6GJVhZf76Tb1BB76t9RdwRilgVOdJqEp5Ogc5FZ5zYb78Mi9O FYxw9RVR0EvFn+QDywZpRQ32gxKhars9dff2nIQHK7B2RbmYe8i3gkeGVD6LiTN9MBxm fJDYindH92MQD42U5PUXkaOw97OKGZe868Zcmg+StWPvFZ5PyYAKv+M2cP3NnKOukbvh fmb4DfEFjuWPYsO4RTETiZneINm5bP4jXjjQ5tXARc74ved3dXqEN6g7J/IygRfAWKXE DxYQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=L1JMuwJe; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h189si12564916pge.86.2022.01.31.03.40.17; Mon, 31 Jan 2022 03:40:28 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=L1JMuwJe; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243885AbiA1Vb3 (ORCPT + 99 others); Fri, 28 Jan 2022 16:31:29 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:52841 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236333AbiA1Vb1 (ORCPT ); Fri, 28 Jan 2022 16:31:27 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1643405486; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=cPaaPTwaHnrZy5BBxHC8AwDN/oX7cxF5Nc5fiuL/xAs=; b=L1JMuwJe5kfMqxQiPSc02NKDIsEuZ6FkbEfmxIa0wffJxLyJpgbSZnI9p/c48Kxop+6aEw D6gzfYmDfsvWiyHhND65z6sOuPOOuPs5A0ok1UW44DVqnk7oZ/kq+/yRm/37fZP7B3br5V 83QAaa501fO2h47uoe2EamSZzPrSEi0= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-70-vIGYNqzuMMah-cPnGiTNJQ-1; Fri, 28 Jan 2022 16:31:23 -0500 X-MC-Unique: vIGYNqzuMMah-cPnGiTNJQ-1 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 mimecast-mx01.redhat.com (Postfix) with ESMTPS id 84FD5814243; Fri, 28 Jan 2022 21:31:21 +0000 (UTC) Received: from [10.22.33.1] (unknown [10.22.33.1]) by smtp.corp.redhat.com (Postfix) with ESMTP id 42AE8E2FE; Fri, 28 Jan 2022 21:31:08 +0000 (UTC) Message-ID: Date: Fri, 28 Jan 2022 16:31:07 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.4.0 Subject: Re: [PATCH 2/2] mm/page_owner: Dump memcg information Content-Language: en-US To: Ira Weiny Cc: Johannes Weiner , Michal Hocko , Vladimir Davydov , Andrew Morton , linux-kernel@vger.kernel.org, cgroups@vger.kernel.org, linux-mm@kvack.org, Rafael Aquini References: <20220128195642.416743-1-longman@redhat.com> <20220128195642.416743-3-longman@redhat.com> <20220128212249.GI785175@iweiny-DESK2.sc.intel.com> From: Waiman Long In-Reply-To: <20220128212249.GI785175@iweiny-DESK2.sc.intel.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/28/22 16:22, Ira Weiny wrote: > On Fri, Jan 28, 2022 at 02:56:42PM -0500, Waiman Long wrote: >> It was found that a number of offlined memcgs were not freed because >> they were pinned by some charged pages that were present. Even "echo >> 1 > /proc/sys/vm/drop_caches" wasn't able to free those pages. These >> offlined but not freed memcgs tend to increase in number over time with >> the side effect that percpu memory consumption as shown in /proc/meminfo >> also increases over time. >> >> In order to find out more information about those pages that pin >> offlined memcgs, the page_owner feature is extended to dump memory >> cgroup information especially whether the cgroup is offlined or not. >> >> Signed-off-by: Waiman Long >> --- >> mm/page_owner.c | 28 ++++++++++++++++++++++++++++ >> 1 file changed, 28 insertions(+) >> >> diff --git a/mm/page_owner.c b/mm/page_owner.c >> index c52ce9d6bc3b..e5d8c642296b 100644 >> --- a/mm/page_owner.c >> +++ b/mm/page_owner.c >> @@ -10,6 +10,7 @@ >> #include >> #include >> #include >> +#include >> #include >> >> #include "internal.h" >> @@ -339,6 +340,7 @@ print_page_owner(char __user *buf, size_t count, unsigned long pfn, >> depot_stack_handle_t handle) >> { >> int ret = 0, pageblock_mt, page_mt; >> + unsigned long __maybe_unused memcg_data; >> char *kbuf; >> >> count = min_t(size_t, count, PAGE_SIZE); >> @@ -371,6 +373,32 @@ print_page_owner(char __user *buf, size_t count, unsigned long pfn, >> "Page has been migrated, last migrate reason: %s\n", >> migrate_reason_names[page_owner->last_migrate_reason]); >> >> +#ifdef CONFIG_MEMCG >> + /* >> + * Look for memcg information and print it out >> + */ >> + memcg_data = READ_ONCE(page->memcg_data); >> + if (memcg_data) { >> + struct mem_cgroup *memcg = page_memcg_check(page); >> + bool onlined; >> + char name[80]; >> + >> + if (memcg_data & MEMCG_DATA_OBJCGS) >> + SNPRINTF(kbuf, count, ret, err, "Slab cache page\n"); >> + >> + if (!memcg) >> + goto copy_out; >> + >> + onlined = (memcg->css.flags & CSS_ONLINE); >> + cgroup_name(memcg->css.cgroup, name, sizeof(name) - 1); >> + SNPRINTF(kbuf, count, ret, err, "Charged %sto %smemcg %s\n", > ^^^ > Extra specifier? > > Did this compile without warnings? Yes, there was no warning. Cheers, Longmna > Ira > >> + PageMemcgKmem(page) ? "(via objcg) " : "", >> + onlined ? "" : "offlined ", name); >> + } >> + >> +copy_out: >> +#endif >> + >> SNPRINTF(kbuf, count, ret, err, "\n"); >> >> if (copy_to_user(buf, kbuf, ret)) >> -- >> 2.27.0 >> >>