From: Waiman Long <longman@redhat.com>
To: Ira Weiny <ira.weiny@intel.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
linux-mm@kvack.org, Rafael Aquini <aquini@redhat.com>
Subject: Re: [PATCH 2/2] mm/page_owner: Dump memcg information
Date: Fri, 28 Jan 2022 16:31:07 -0500 [thread overview]
Message-ID: <e14e8c96-b2e3-cb57-2c35-284116798225@redhat.com> (raw)
In-Reply-To: <20220128212249.GI785175@iweiny-DESK2.sc.intel.com>
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 <longman@redhat.com>
>> ---
>> 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 <linux/migrate.h>
>> #include <linux/stackdepot.h>
>> #include <linux/seq_file.h>
>> +#include <linux/memcontrol.h>
>> #include <linux/sched/clock.h>
>>
>> #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
>>
>>
next prev parent reply other threads:[~2022-01-28 21:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 19:56 [PATCH 0/2] mm/page_owner: Extend page_owner to show memcg Waiman Long
2022-01-28 19:56 ` [PATCH 1/2] mm/page_owner: Introduce SNPRINTF() macro that includes length error check Waiman Long
2022-01-28 21:18 ` Ira Weiny
2022-01-28 21:22 ` Waiman Long
2022-01-28 19:56 ` [PATCH 2/2] mm/page_owner: Dump memcg information Waiman Long
2022-01-28 21:22 ` Ira Weiny
2022-01-28 21:31 ` Waiman Long [this message]
2022-01-28 21:48 ` Ira Weiny
2022-01-29 3:35 ` Waiman Long
2022-01-29 4:05 ` Ira Weiny
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=e14e8c96-b2e3-cb57-2c35-284116798225@redhat.com \
--to=longman@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=aquini@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=ira.weiny@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=vdavydov.dev@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox