From: David Laight <david.laight.linux@gmail.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Xie Yuanbin <qq570070308@gmail.com>,
akpm@linux-foundation.org, david@kernel.org, ljs@kernel.org,
Liam.Howlett@oracle.com, vbabka@kernel.org, surenb@google.com,
mhocko@suse.com, nathan@kernel.org,
nick.desaulniers+lkml@gmail.com, morbo@google.com,
justinstitt@google.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] mm: optimize once judgment with clang
Date: Sat, 7 Mar 2026 10:48:55 +0000 [thread overview]
Message-ID: <20260307104855.1de4fc28@pumpkin> (raw)
In-Reply-To: <aavd4hoAO1DFLuJP@kernel.org>
On Sat, 7 Mar 2026 10:12:18 +0200
Mike Rapoport <rppt@kernel.org> wrote:
> On Sat, Mar 07, 2026 at 02:54:04PM +0800, Xie Yuanbin wrote:
> > commit 242b872239f6a7deacbc ("include/linux/once_lite.h: fix judgment in
> > WARN_ONCE with clang") helps optimize performance and size under the
> > clang compiler, but the modification is not complete.
>
> How much does it actually optimize for size?
> Note that performance is really not critical here because we are already
> dealing with slow path of debug code.
I suspect that unlikely(a && b) is really horrid - the compiler could
easily generate x = a && b; unlikely(x).
Probably enough to change to unlikely(a) && b, but if it is a slow path
perhaps just remove the unlikely().
David
>
> > Port the modification to WARN_ON_ONCE_GFP(), VM_WARN_ON_ONCE_PAGE(),
> > VM_WARN_ON_ONCE_FOLIO(), VM_WARN_ON_ONCE_MM() and VM_WARN_ON_ONCE_VMA().
> >
> > Cc: Andrew Morton <akpm@linux-foundation.org>
> > Signed-off-by: Xie Yuanbin <qq570070308@gmail.com>
> > ---
> > include/linux/mmdebug.h | 8 ++++----
> > mm/internal.h | 3 ++-
> > 2 files changed, 6 insertions(+), 5 deletions(-)
> >
> > diff --git a/include/linux/mmdebug.h b/include/linux/mmdebug.h
> > index ab60ffba08f5..a167c5aa525e 100644
> > --- a/include/linux/mmdebug.h
> > +++ b/include/linux/mmdebug.h
> > @@ -60,7 +60,7 @@ void vma_iter_dump_tree(const struct vma_iterator *vmi);
> > static bool __section(".data..once") __warned; \
> > int __ret_warn_once = !!(cond); \
> > \
> > - if (unlikely(__ret_warn_once && !__warned)) { \
> > + if (unlikely(__ret_warn_once) && unlikely(!__warned)) { \
> > dump_page(page, "VM_WARN_ON_ONCE_PAGE(" __stringify(cond)")");\
> > __warned = true; \
> > WARN_ON(1); \
> > @@ -80,7 +80,7 @@ void vma_iter_dump_tree(const struct vma_iterator *vmi);
> > static bool __section(".data..once") __warned; \
> > int __ret_warn_once = !!(cond); \
> > \
> > - if (unlikely(__ret_warn_once && !__warned)) { \
> > + if (unlikely(__ret_warn_once) && unlikely(!__warned)) { \
> > dump_page(&folio->page, "VM_WARN_ON_ONCE_FOLIO(" __stringify(cond)")");\
> > __warned = true; \
> > WARN_ON(1); \
> > @@ -91,7 +91,7 @@ void vma_iter_dump_tree(const struct vma_iterator *vmi);
> > static bool __section(".data..once") __warned; \
> > int __ret_warn_once = !!(cond); \
> > \
> > - if (unlikely(__ret_warn_once && !__warned)) { \
> > + if (unlikely(__ret_warn_once) && unlikely(!__warned)) { \
> > dump_mm(mm); \
> > __warned = true; \
> > WARN_ON(1); \
> > @@ -102,7 +102,7 @@ void vma_iter_dump_tree(const struct vma_iterator *vmi);
> > static bool __section(".data..once") __warned; \
> > int __ret_warn_once = !!(cond); \
> > \
> > - if (unlikely(__ret_warn_once && !__warned)) { \
> > + if (unlikely(__ret_warn_once) && unlikely(!__warned)) { \
> > dump_vma(vma); \
> > __warned = true; \
> > WARN_ON(1); \
> > diff --git a/mm/internal.h b/mm/internal.h
> > index 6e1162e13289..52367f52d623 100644
> > --- a/mm/internal.h
> > +++ b/mm/internal.h
> > @@ -93,7 +93,8 @@ struct pagetable_move_control {
> > static bool __section(".data..once") __warned; \
> > int __ret_warn_once = !!(cond); \
> > \
> > - if (unlikely(!(gfp & __GFP_NOWARN) && __ret_warn_once && !__warned)) { \
> > + if (unlikely(__ret_warn_once) && !(gfp & __GFP_NOWARN) && \
> > + unlikely(!__warned)) { \
> > __warned = true; \
> > WARN_ON(1); \
> > } \
> > --
> > 2.51.0
> >
>
next prev parent reply other threads:[~2026-03-07 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 6:54 [PATCH] mm: optimize once judgment with clang Xie Yuanbin
2026-03-07 8:12 ` Mike Rapoport
2026-03-07 10:48 ` David Laight [this message]
2026-03-07 14:41 ` Xie Yuanbin
2026-03-08 18:03 ` Mike Rapoport
2026-03-09 15:32 ` Xie Yuanbin
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=20260307104855.1de4fc28@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mhocko@suse.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=qq570070308@gmail.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
/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