From: SeongJae Park <sj@kernel.org>
To: Shakeel Butt <shakeel.butt@linux.dev>
Cc: SeongJae Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.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: manually uninline __memcg_memory_event
Date: Tue, 21 Oct 2025 17:58:00 -0700 [thread overview]
Message-ID: <20251022005801.120250-1-sj@kernel.org> (raw)
In-Reply-To: <20251021234425.1885471-1-shakeel.butt@linux.dev>
On Tue, 21 Oct 2025 16:44:25 -0700 Shakeel Butt <shakeel.butt@linux.dev> wrote:
> The function __memcg_memory_event has been unnecessarily marked inline
> even when it is not really performance critical. It is usually called
> to track extreme conditions. Over the time, it has evolved to include
> more functionality and inlining it is causing more harm.
>
> Before the patch:
> $ size mm/memcontrol.o net/ipv4/tcp_input.o net/ipv4/tcp_output.o
> text data bss dec hex filename
> 35645 10574 4192 50411 c4eb mm/memcontrol.o
> 54738 1658 0 56396 dc4c net/ipv4/tcp_input.o
> 34644 1065 0 35709 8b7d net/ipv4/tcp_output.o
>
> After the patch:
> $ size mm/memcontrol.o net/ipv4/tcp_input.o net/ipv4/tcp_output.o
> text data bss dec hex filename
> 35137 10446 4192 49775 c26f mm/memcontrol.o
> 54322 1562 0 55884 da4c net/ipv4/tcp_input.o
> 34492 1017 0 35509 8ab5 net/ipv4/tcp_output.o
>
> Signed-off-by: Shakeel Butt <shakeel.butt@linux.dev>
> ---
> include/linux/memcontrol.h | 32 ++------------------------------
> mm/memcontrol.c | 31 +++++++++++++++++++++++++++++++
> 2 files changed, 33 insertions(+), 30 deletions(-)
>
> diff --git a/include/linux/memcontrol.h b/include/linux/memcontrol.h
> index d37e7c93bb8c..8d2e250535a8 100644
> --- a/include/linux/memcontrol.h
> +++ b/include/linux/memcontrol.h
> @@ -1002,36 +1002,8 @@ static inline void count_memcg_event_mm(struct mm_struct *mm,
> count_memcg_events_mm(mm, idx, 1);
> }
>
> -static inline void __memcg_memory_event(struct mem_cgroup *memcg,
> - enum memcg_memory_event event,
> - bool allow_spinning)
> -{
> - bool swap_event = event == MEMCG_SWAP_HIGH || event == MEMCG_SWAP_MAX ||
> - event == MEMCG_SWAP_FAIL;
> -
> - /* For now only MEMCG_MAX can happen with !allow_spinning context. */
> - VM_WARN_ON_ONCE(!allow_spinning && event != MEMCG_MAX);
> -
> - atomic_long_inc(&memcg->memory_events_local[event]);
> - if (!swap_event && allow_spinning)
> - cgroup_file_notify(&memcg->events_local_file);
> -
> - do {
> - atomic_long_inc(&memcg->memory_events[event]);
> - if (allow_spinning) {
> - if (swap_event)
> - cgroup_file_notify(&memcg->swap_events_file);
> - else
> - cgroup_file_notify(&memcg->events_file);
> - }
> -
> - if (!cgroup_subsys_on_dfl(memory_cgrp_subsys))
> - break;
> - if (cgrp_dfl_root.flags & CGRP_ROOT_MEMORY_LOCAL_EVENTS)
> - break;
> - } while ((memcg = parent_mem_cgroup(memcg)) &&
> - !mem_cgroup_is_root(memcg));
> -}
> +void __memcg_memory_event(struct mem_cgroup *memcg,
> + enum memcg_memory_event event, bool allow_spinning);
>
> static inline void memcg_memory_event(struct mem_cgroup *memcg,
> enum memcg_memory_event event)
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index 1a95049d8b88..93f7c76f0ce9 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -1626,6 +1626,37 @@ unsigned long mem_cgroup_size(struct mem_cgroup *memcg)
> return page_counter_read(&memcg->memory);
> }
>
> +void __memcg_memory_event(struct mem_cgroup *memcg,
> + enum memcg_memory_event event, bool allow_spinning)
Seems this function is called only from memcontrol.c. Why not making it a
static function?
> +{
> + bool swap_event = event == MEMCG_SWAP_HIGH || event == MEMCG_SWAP_MAX ||
> + event == MEMCG_SWAP_FAIL;
> +
> + /* For now only MEMCG_MAX can happen with !allow_spinning context. */
> + VM_WARN_ON_ONCE(!allow_spinning && event != MEMCG_MAX);
> +
> + atomic_long_inc(&memcg->memory_events_local[event]);
> + if (!swap_event && allow_spinning)
> + cgroup_file_notify(&memcg->events_local_file);
> +
> + do {
> + atomic_long_inc(&memcg->memory_events[event]);
> + if (allow_spinning) {
> + if (swap_event)
> + cgroup_file_notify(&memcg->swap_events_file);
> + else
> + cgroup_file_notify(&memcg->events_file);
> + }
> +
> + if (!cgroup_subsys_on_dfl(memory_cgrp_subsys))
> + break;
> + if (cgrp_dfl_root.flags & CGRP_ROOT_MEMORY_LOCAL_EVENTS)
> + break;
> + } while ((memcg = parent_mem_cgroup(memcg)) &&
> + !mem_cgroup_is_root(memcg));
> +}
> +EXPORT_SYMBOL(__memcg_memory_event);
Also, seems there is no reason to export this symbol?
Thanks,
SJ
[...]
next prev parent reply other threads:[~2025-10-22 0:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 23:44 Shakeel Butt
2025-10-22 0:58 ` SeongJae Park [this message]
2025-10-22 1:28 ` Shakeel Butt
2025-10-22 2:15 ` SeongJae Park
2025-10-22 18:10 ` Roman Gushchin
2025-10-23 13:18 ` Michal Hocko
2025-10-23 21:35 ` Shakeel Butt
2025-10-24 6:50 ` Michal Hocko
2025-10-27 7:19 ` Christoph Hellwig
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=20251022005801.120250-1-sj@kernel.org \
--to=sj@kernel.org \
--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=mhocko@kernel.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