From: Heiko Carstens <hca@linux.ibm.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Hao Ge <hao.ge@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
Suren Baghdasaryan <surenb@google.com>,
Richard Henderson <richard.henderson@linaro.org>,
Matt Turner <mattst88@gmail.com>, Dennis Zhou <dennis@kernel.org>,
Tejun Heo <tj@kernel.org>, Christoph Lameter <cl@linux.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-alpha@vger.kernel.org, linux-s390@vger.kernel.org,
Hao Ge <gehao@kylinos.cn>
Subject: Re: [PATCH 5/5] mm/alloc_tag: add the CONFIG_ARCH_NEEDS_WEAK_PER_CPU macro when statically defining the percpu variable _shared_alloc_tag
Date: Thu, 12 Jun 2025 13:24:44 +0200 [thread overview]
Message-ID: <20250612112444.10868E66-hca@linux.ibm.com> (raw)
In-Reply-To: <aEqWjSSLB3TPt9CH@kernel.org>
On Thu, Jun 12, 2025 at 11:57:49AM +0300, Mike Rapoport wrote:
> On Thu, Jun 12, 2025 at 04:27:30PM +0800, Hao Ge wrote:
> > From: Hao Ge <gehao@kylinos.cn>
> >
> > Recently discovered this entry while checking kallsyms on ARM64:
> > ffff800083e509c0 D _shared_alloc_tag
> >
> > If CONFIG_ARCH_NEEDS_WEAK_PER_CPU is not defined(it is only defined for
> > s390 and alpha architectures),there's no need to statically define
> > the percpu variable _shared_alloc_tag. As the number of CPUs
> > increases,the wasted memory will grow correspondingly.
> >
> > Enclose the definition of _shared_alloc_tag within the
> > CONFIG_ARCH_NEEDS_WEAK_PER_CPU condition.
> >
> > Suggested-by: Suren Baghdasaryan <surenb@google.com>
> > Signed-off-by: Hao Ge <gehao@kylinos.cn>
> > ---
> > lib/alloc_tag.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/lib/alloc_tag.c b/lib/alloc_tag.c
> > index c7f602fa7b23..14fd66f26e42 100644
> > --- a/lib/alloc_tag.c
> > +++ b/lib/alloc_tag.c
> > @@ -24,8 +24,10 @@ static bool mem_profiling_support;
> >
> > static struct codetag_type *alloc_tag_cttype;
> >
> > +#ifdef CONFIG_ARCH_NEEDS_WEAK_PER_CPU
>
> It should be enough to add #ifdef ARCH_NEEDS_WEAK_PER_CPU here instead of
> all the churn.
That won't work since ARCH_NEEDS_WEAK_PER_CPU is only defined if MODULE is
also defined, which is not the case for core kernel code like lib/alloc_tag.c.
As a side note: I'm wondering if s390 still needs ARCH_NEEDS_WEAK_PER_CPU due
to all the compiler option changes we had recently. But that's a different
story and independent of this series.
prev parent reply other threads:[~2025-06-12 11:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 8:27 [PATCH 0/5] mm: Restrict the static definition of the per-CPU variable _shared_alloc_tag to s390 and alpha architectures only Hao Ge
2025-06-12 8:27 ` [PATCH 1/5] mm/Kconfig: add ARCH_NEEDS_WEAK_PER_CPU option Hao Ge
2025-06-12 8:27 ` [PATCH 2/5] alpha: Modify the definition logic of WEAK_PER_CPU Hao Ge
2025-06-12 11:22 ` Heiko Carstens
2025-06-12 12:06 ` Hao Ge
2025-06-12 12:15 ` Heiko Carstens
2025-06-12 8:27 ` [PATCH 3/5] s390: " Hao Ge
2025-06-12 8:27 ` [PATCH 4/5] mm: use MODULE_NEEDS_WEAK_PER_CPU instead of ARCH_NEEDS_WEAK_PER_CPU Hao Ge
2025-06-12 8:27 ` [PATCH 5/5] mm/alloc_tag: add the CONFIG_ARCH_NEEDS_WEAK_PER_CPU macro when statically defining the percpu variable _shared_alloc_tag Hao Ge
2025-06-12 8:57 ` Mike Rapoport
2025-06-12 11:24 ` Heiko Carstens [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=20250612112444.10868E66-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=Liam.Howlett@oracle.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@linux.ibm.com \
--cc=cl@linux.com \
--cc=david@redhat.com \
--cc=dennis@kernel.org \
--cc=gehao@kylinos.cn \
--cc=gor@linux.ibm.com \
--cc=hao.ge@linux.dev \
--cc=kent.overstreet@linux.dev \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mattst88@gmail.com \
--cc=richard.henderson@linaro.org \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=svens@linux.ibm.com \
--cc=tj@kernel.org \
--cc=vbabka@suse.cz \
/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