From: Joonwon Kang <joonwonkang@google.com>
To: visitorckw@gmail.com
Cc: akpm@linux-foundation.org, cl@gentwo.org, dennis@kernel.org,
dodam@google.com, joonwonkang@google.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, tj@kernel.org
Subject: Re: [PATCH v2] percpu: Fix hint invariant breakage
Date: Fri, 10 Apr 2026 17:49:50 +0000 [thread overview]
Message-ID: <20260410174950.1454063-1-joonwonkang@google.com> (raw)
In-Reply-To: <adfb1wrzJjuqHEuA@google.com>
> Hi Joonwon,
>
> On Wed, Apr 08, 2026 at 10:06:42AM +0000, Joonwon Kang wrote:
> > The invariant "scan_hint_start > contig_hint_start if and only if
> > scan_hint == contig_hint" should be kept for hint management. However,
> > it could be broken in some cases:
> >
> > - if (new contig == contig_hint == scan_hint) && (contig_hint_start <
> > scan_hint_start < new contig start) && the new contig is to become a
> > new contig_hint due to its better alignment, then scan_hint should
> > be invalidated instead of keeping the old value.
> >
> > - if (new contig == contig_hint > scan_hint) && (new contig start <
> > contig_hint_start) && the new contig is not to become a new
> > contig_hint, then scan_hint should be not updated to the new contig.
> >
> > This commit refactors the percpu block update code to make it more
> > visible on what to consider, e.g. when the new contig overlaps with the
> > old contig_hint or scan_hint, fixes the invariant breakage and also
> > optimizes scan_hint further. Some of the optimization cases when no
> > overlap occurs are:
> >
> > - if (new contig > contig_hint > scan_hint) && (scan_hint_start < new
> > contig start < contig_hint_start), then keep scan_hint instead of
> > invalidating it.
> >
> > - if (new contig > contig_hint == scan_hint) && (contig_hint_start <
> > new contig start < scan_hint_start), then update scan_hint to the
> > old contig_hint instead of invalidating it.
> >
> > - if (new contig == contig_hint > scan_hint) && (new contig start <
> > contig_hint_start) && the new contig is to become a new contig_hint
> > due to its better alignment, then update scan_hint to the old
> > contig_hint instead of invalidating or keeping it.
> >
> > Signed-off-by: Joonwon Kang <joonwonkang@google.com>
> > ---
> > v1 -> v2: Consider cases where the new contig overlaps with the existing
> > contig_hint or scan_hint.
> >
> > mm/percpu.c | 124 +++++++++++++++++++++++++++++++++++-----------------
> > 1 file changed, 85 insertions(+), 39 deletions(-)
> >
>
> Just a few minor style nits; checkpatch.pl reported the following:
>
> CHECK: Lines should not end with a '('
> #173: FILE: mm/percpu.c:653:
> + overlap_with_contig_hint = pcpu_region_overlap(
>
> CHECK: Unnecessary parentheses around 'scan_hint_cand_2 > scan_hint_cand_1'
> #258: FILE: mm/percpu.c:699:
> + if ((scan_hint_cand_2 > scan_hint_cand_1) ||
> + (scan_hint_cand_2 == scan_hint_cand_1 &&
> + scan_hint_cand_2_start > scan_hint_cand_1_start)) {
>
> Since this patch will need a respin anyway, I think it would be better
> to address these together in the next version.
>
> Regards,
> Kuan-Wei
Hey, thanks for running style checker for me. As it looked fine when I ran it,
I guess you may have run it with `--strict` option. I am not sure if the strict
option is required. I will keep it as-is since it does not seem very important
unless it hurts readability. Please let me know if you think it is.
Thanks,
Joonwon Kang
prev parent reply other threads:[~2026-04-10 17:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 10:06 [PATCH v2] percpu: Fix hint invariant breakage Joonwon Kang
2026-04-08 11:04 ` Joonwon Kang
2026-04-09 17:03 ` Kuan-Wei Chiu
2026-04-10 17:49 ` Joonwon Kang [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=20260410174950.1454063-1-joonwonkang@google.com \
--to=joonwonkang@google.com \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=dennis@kernel.org \
--cc=dodam@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tj@kernel.org \
--cc=visitorckw@gmail.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