From: Michal Hocko <mhocko@suse.com>
To: Shakeel Butt <shakeel.butt@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org,
Meta kernel team <kernel-team@meta.com>
Subject: Re: [PATCH] memcg: move do_memsw_account() to CONFIG_MEMCG_V1
Date: Thu, 13 Mar 2025 08:33:48 +0100 [thread overview]
Message-ID: <Z9KKXF-CSYuGKSXW@tiehlicka> (raw)
In-Reply-To: <20250312222552.3284173-1-shakeel.butt@linux.dev>
On Wed 12-03-25 15:25:52, Shakeel Butt wrote:
> The do_memsw_account() is used to enable or disable legacy memory+swap
> accounting in memory cgroup. However with disabled CONFIG_MEMCG_V1, we
> don't need to keep checking it. So, let's always return false for
> !CONFIG_MEMCG_V1 configs.
>
> Before the patch:
>
> $ size mm/memcontrol.o
> text data bss dec hex filename
> 49928 10736 4172 64836 fd44 mm/memcontrol.o
>
> After the patch:
>
> $ size mm/memcontrol.o
> text data bss dec hex filename
> 49430 10480 4172 64082 fa52 mm/memcontrol.o
>
> Signed-off-by: Shakeel Butt <shakeel.butt@linux.dev>
Acked-by: Michal Hocko <mhocko@suse.com>
Thanks!
> ---
> mm/memcontrol-v1.h | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/mm/memcontrol-v1.h b/mm/memcontrol-v1.h
> index 653ff1bad244..6358464bb416 100644
> --- a/mm/memcontrol-v1.h
> +++ b/mm/memcontrol-v1.h
> @@ -22,12 +22,6 @@
> iter != NULL; \
> iter = mem_cgroup_iter(NULL, iter, NULL))
>
> -/* Whether legacy memory+swap accounting is active */
> -static inline bool do_memsw_account(void)
> -{
> - return !cgroup_subsys_on_dfl(memory_cgrp_subsys);
> -}
> -
> unsigned long mem_cgroup_usage(struct mem_cgroup *memcg, bool swap);
>
> void drain_all_stock(struct mem_cgroup *root_memcg);
> @@ -42,6 +36,12 @@ struct mem_cgroup *mem_cgroup_id_get_online(struct mem_cgroup *memcg);
> /* Cgroup v1-specific declarations */
> #ifdef CONFIG_MEMCG_V1
>
> +/* Whether legacy memory+swap accounting is active */
> +static inline bool do_memsw_account(void)
> +{
> + return !cgroup_subsys_on_dfl(memory_cgrp_subsys);
> +}
> +
> unsigned long memcg_events_local(struct mem_cgroup *memcg, int event);
> unsigned long memcg_page_state_local(struct mem_cgroup *memcg, int idx);
> unsigned long memcg_page_state_local_output(struct mem_cgroup *memcg, int item);
> @@ -94,6 +94,7 @@ extern struct cftype mem_cgroup_legacy_files[];
>
> #else /* CONFIG_MEMCG_V1 */
>
> +static inline bool do_memsw_account(void) { return false; }
> static inline bool memcg1_alloc_events(struct mem_cgroup *memcg) { return true; }
> static inline void memcg1_free_events(struct mem_cgroup *memcg) {}
>
> --
> 2.47.1
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2025-03-13 7:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 22:25 Shakeel Butt
2025-03-12 23:01 ` Johannes Weiner
2025-03-13 7:33 ` Michal Hocko [this message]
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=Z9KKXF-CSYuGKSXW@tiehlicka \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
/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