All of lore.kernel.org
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
To: gregkh@linuxfoundation.org
Cc: SJ Park <sj@kernel.org>,
	akpm@linux-foundation.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] mm/damon/ops-common: use nr_accesses moving sum for quota" failed to apply to 6.6-stable tree
Date: Tue,  8 Sep 2026 22:23:56 -0700	[thread overview]
Message-ID: <20260909052357.235575-1-sj@kernel.org> (raw)
In-Reply-To: <2026090847-trapdoor-essence-0783@gregkh>

On Tue, 08 Sep 2026 14:52:47 +0200 <gregkh@linuxfoundation.org> wrote:

> 
> The patch below does not apply to the 6.6-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
[...]
> ------------------ original commit in Linus's tree ------------------
> 
> From 6c25083f7ae7e2660d766169e5b4d3e96010503f Mon Sep 17 00:00:00 2001
> From: SJ Park <sj@kernel.org>
> Date: Sun, 19 Jul 2026 09:11:33 -0700
> Subject: [PATCH] mm/damon/ops-common: use nr_accesses moving sum for quota
>  score
> 
> Since commit 42f994b71404 ("mm/damon/core: implement scheme-specific apply
> interval"), DAMOS scheme can be applied at any time.  At that time,
> nr_accesses may not be fully aggregated.  But the quota prioritization
> score is calculated using the not fully aggregated count.  As a result,
> the performance of DAMOS could be degraded.  Fix by using
> damon_nr_accesses_mvsum() instead.
> 
> The user impact of the issue is suboptimum DAMOS performance under certain
> setups.  Nonetheless, the bug was there from the beginning of the setup
> availability.  In other words, the suboptimum performance is the baseline
> of the setup and hence it didn't cause regression.  Also the extent of the
> suboptimality was not big enough to be found from users and testers.
> Still, this is a clear bug that is better to be fixed, and can be easily
> fixed.
> 
> Link: https://lore.kernel.org/20260719161136.90191-1-sj@kernel.org
> Fixes: 42f994b71404 ("mm/damon/core: implement scheme-specific apply interval")

Seems the broken commit is backported to 6.6.y even though it is not a fix,
maybe to resolve a conflict of another fix.  That should be why this patch is
tried to be applied on 6.6.y.

Though the broken commit indeed introduced the feature to DAMON API, the commit
didn't introduce any DAMON API caller that uses the feature.  Apparently commit
a2a9f68e358f ("mm/damon/sysfs-schemes: support DAMOS apply interval") has
further integrated the feature with DAMON sysfs interface, and exposed it to
users.  So technically speaking, it is the real broken commit.

And the real broken commit is not in 6.6.y.  So, this patch is not really
needed for 6.6.y.


Thanks,
SJ

[...]

      reply	other threads:[~2026-09-09  5:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 12:52 FAILED: patch "[PATCH] mm/damon/ops-common: use nr_accesses moving sum for quota" failed to apply to 6.6-stable tree gregkh
2026-09-09  5:23 ` SJ Park [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=20260909052357.235575-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.