From: Andrew Morton <akpm@linux-foundation.org>
To: Barry Song <21cnbao@gmail.com>
Cc: "David Hildenbrand (Red Hat)" <david@kernel.org>,
Wale Zhang <wale.zhang.ftd@gmail.com>,
chrisl@kernel.org, ziy@nvidia.com, lorenzo.stoakes@oracle.com,
matthew.brost@intel.com, linux-mm@kvack.org
Subject: Re: [PATCH v2] mm/swapops,rmap: remove should-never-be-compiled codes.
Date: Tue, 30 Dec 2025 13:35:22 -0800 [thread overview]
Message-ID: <20251230133522.e15135c3a17826428f472a2e@linux-foundation.org> (raw)
In-Reply-To: <CAGsJ_4w=KuVs5+p+3gZ=L7=rzA3qgnMVQOBJNBEPnMDWx2N+dg@mail.gmail.com>
On Wed, 31 Dec 2025 10:28:25 +1300 Barry Song <21cnbao@gmail.com> wrote:
> On Wed, Dec 31, 2025 at 8:50 AM David Hildenbrand (Red Hat)
> <david@kernel.org> wrote:
> >
> >
> > > - break;
> > > +#ifdef CONFIG_NO_PAGE_MAPCOUNT
> > > + last = atomic_add_negative(-1, &folio->_entire_mapcount);
> > > + if (level == PGTABLE_LEVEL_PMD && last)
> > > + nr_pmdmapped = folio_large_nr_pages(folio);
> > > + nr = folio_dec_return_large_mapcount(folio, vma);
> > > + if (!nr) {
> > > + /* Now completely unmapped. */
> > > + nr = folio_large_nr_pages(folio);
> > > + } else {
> > > + partially_mapped = last &&
> > > + nr < folio_large_nr_pages(folio);
> > > + nr = 0;
> >
> > The whole code was written to avoid ifdefs.
>
> The #ifdefs are only for -O0 builds, which are never a
> mainline requirement. However, dropping functions that
> contain nothing but a BUILD_BUG() seems reasonable?
Let's not make -O0 an objective, please. We often make assumptions
about dead code elimination in order to keep kernel code more pleasing
to read and to maintain.
> If those functions were actually required, the compiler
> would fail anyway. In that case, there doesn’t seem to be
> much value in keeping wrapper functions whose sole purpose
> is to contain a single BUILD_BUG().
I agree with that part of the patch - if the thing only does a
BUILD_BUG() then let's simply remove it. If somehow the compiler tries
to reference the now-not-present function then we'll get an error message
anyway.
next prev parent reply other threads:[~2025-12-30 21:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 13:01 Wale Zhang
2025-12-30 18:10 ` Andrew Morton
2025-12-30 19:50 ` David Hildenbrand (Red Hat)
2025-12-30 21:28 ` Barry Song
2025-12-30 21:35 ` Andrew Morton [this message]
2025-12-30 21:59 ` David Hildenbrand (Red Hat)
2025-12-31 11:58 ` wale zhang
2025-12-31 12:17 ` David Hildenbrand (Red Hat)
2025-12-31 9:30 ` wale zhang
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=20251230133522.e15135c3a17826428f472a2e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=21cnbao@gmail.com \
--cc=chrisl@kernel.org \
--cc=david@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=matthew.brost@intel.com \
--cc=wale.zhang.ftd@gmail.com \
--cc=ziy@nvidia.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: 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