From: Roman Gushchin <guro@fb.com> To: Michal Hocko <mhocko@kernel.org> Cc: Johannes Weiner <hannes@cmpxchg.org>, Tejun Heo <tj@kernel.org>, Li Zefan <lizefan@huawei.com>, Vladimir Davydov <vdavydov.dev@gmail.com>, <cgroups@vger.kernel.org>, <linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org> Subject: Re: [PATCH] mm: per-cgroup memory reclaim stats Date: Tue, 16 May 2017 14:13:16 +0100 [thread overview] Message-ID: <20170516131316.GA7834@castle> (raw) In-Reply-To: <20170516092956.GF2481@dhcp22.suse.cz> Hi Michal! On Tue, May 16, 2017 at 11:29:56AM +0200, Michal Hocko wrote: > On Thu 11-05-17 20:16:23, Roman Gushchin wrote: > > Track the following reclaim counters for every memory cgroup: > > PGREFILL, PGSCAN, PGSTEAL, PGACTIVATE, PGDEACTIVATE, PGLAZYFREE and > > PGLAZYFREED. > > yes, those are definitely useful. I have an old patch to add them as > well but never managed to clean it up and post... > > > These values are exposed using the memory.stats interface of cgroup v2. > > Is there any reason to not add them to v1? Not really, I'm just not sure, if it worth it to change v1 interface here. If you want, I can add them. > This should be rather trivial after recent changes from Johannes. If you're about memcg1_events[]/memcg1_event_names[], they can't be reused, because the pgscan and pgsteal values are both sums of direct and kswapd values: e.g. events[PGSTEAL_KSWAPD] + events[PGSTEAL_DIRECT]. > > > The meaning of each value is the same as for global counters, > > available using /proc/vmstat. > > > > Also, for consistency, rename mem_cgroup_count_vm_event() to > > count_memcg_event_mm(). > > > > Signed-off-by: Roman Gushchin <guro@fb.com> > > Suggested-by: Johannes Weiner <hannes@cmpxchg.org> > > Cc: Johannes Weiner <hannes@cmpxchg.org> > > Cc: Tejun Heo <tj@kernel.org> > > Cc: Li Zefan <lizefan@huawei.com> > > Cc: Michal Hocko <mhocko@kernel.org> > > Cc: Vladimir Davydov <vdavydov.dev@gmail.com> > > Cc: cgroups@vger.kernel.org > > Cc: linux-doc@vger.kernel.org > > Cc: linux-kernel@vger.kernel.org > > Cc: linux-mm@kvack.org > > the patch itself looks good to me. I will have to double check it after > I am done with what I am doing currently and then will add my Acked-by Thank you!
WARNING: multiple messages have this Message-ID (diff)
From: Roman Gushchin <guro@fb.com> To: Michal Hocko <mhocko@kernel.org> Cc: Johannes Weiner <hannes@cmpxchg.org>, Tejun Heo <tj@kernel.org>, Li Zefan <lizefan@huawei.com>, Vladimir Davydov <vdavydov.dev@gmail.com>, cgroups@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH] mm: per-cgroup memory reclaim stats Date: Tue, 16 May 2017 14:13:16 +0100 [thread overview] Message-ID: <20170516131316.GA7834@castle> (raw) In-Reply-To: <20170516092956.GF2481@dhcp22.suse.cz> Hi Michal! On Tue, May 16, 2017 at 11:29:56AM +0200, Michal Hocko wrote: > On Thu 11-05-17 20:16:23, Roman Gushchin wrote: > > Track the following reclaim counters for every memory cgroup: > > PGREFILL, PGSCAN, PGSTEAL, PGACTIVATE, PGDEACTIVATE, PGLAZYFREE and > > PGLAZYFREED. > > yes, those are definitely useful. I have an old patch to add them as > well but never managed to clean it up and post... > > > These values are exposed using the memory.stats interface of cgroup v2. > > Is there any reason to not add them to v1? Not really, I'm just not sure, if it worth it to change v1 interface here. If you want, I can add them. > This should be rather trivial after recent changes from Johannes. If you're about memcg1_events[]/memcg1_event_names[], they can't be reused, because the pgscan and pgsteal values are both sums of direct and kswapd values: e.g. events[PGSTEAL_KSWAPD] + events[PGSTEAL_DIRECT]. > > > The meaning of each value is the same as for global counters, > > available using /proc/vmstat. > > > > Also, for consistency, rename mem_cgroup_count_vm_event() to > > count_memcg_event_mm(). > > > > Signed-off-by: Roman Gushchin <guro@fb.com> > > Suggested-by: Johannes Weiner <hannes@cmpxchg.org> > > Cc: Johannes Weiner <hannes@cmpxchg.org> > > Cc: Tejun Heo <tj@kernel.org> > > Cc: Li Zefan <lizefan@huawei.com> > > Cc: Michal Hocko <mhocko@kernel.org> > > Cc: Vladimir Davydov <vdavydov.dev@gmail.com> > > Cc: cgroups@vger.kernel.org > > Cc: linux-doc@vger.kernel.org > > Cc: linux-kernel@vger.kernel.org > > Cc: linux-mm@kvack.org > > the patch itself looks good to me. I will have to double check it after > I am done with what I am doing currently and then will add my Acked-by Thank you! -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-05-16 13:14 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-05-11 19:16 [PATCH] mm: per-cgroup memory reclaim stats Roman Gushchin 2017-05-11 19:16 ` Roman Gushchin 2017-05-12 2:25 ` Balbir Singh 2017-05-12 2:25 ` Balbir Singh 2017-05-12 16:42 ` Johannes Weiner 2017-05-12 16:42 ` Johannes Weiner 2017-05-12 16:42 ` Johannes Weiner 2017-05-16 22:03 ` Balbir Singh 2017-05-16 22:03 ` Balbir Singh 2017-05-16 22:03 ` Balbir Singh 2017-05-17 15:50 ` Roman Gushchin 2017-05-17 15:50 ` Roman Gushchin 2017-05-16 9:29 ` Michal Hocko 2017-05-16 9:29 ` Michal Hocko 2017-05-16 9:29 ` Michal Hocko 2017-05-16 13:13 ` Roman Gushchin [this message] 2017-05-16 13:13 ` Roman Gushchin 2017-05-19 10:47 ` Michal Hocko 2017-05-19 10:47 ` Michal Hocko 2017-05-20 19:15 ` Vladimir Davydov 2017-05-20 19:15 ` Vladimir Davydov 2017-05-20 19:15 ` Vladimir Davydov 2017-05-24 15:26 ` Johannes Weiner 2017-05-24 15:26 ` Johannes Weiner
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=20170516131316.GA7834@castle \ --to=guro@fb.com \ --cc=cgroups@vger.kernel.org \ --cc=hannes@cmpxchg.org \ --cc=linux-doc@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=lizefan@huawei.com \ --cc=mhocko@kernel.org \ --cc=tj@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: linkBe 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.