From: sashiko-bot@kernel.org
To: "SeongJae Park" <sj@kernel.org>
Cc: damon@lists.linux.dev
Subject: Re: [RFC PATCH v1.1 12/13] mm/damon/core: remove damon_moving_sum() and its unit test
Date: Sat, 20 Jun 2026 17:35:46 +0000 [thread overview]
Message-ID: <20260620173547.0F18E1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260620172244.90953-13-sj@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The `attrs` parameter in `damon_update_region_access_rate()` is completely unused and should be removed.
--
commit 4c4d26b15dff409f33a357a198fe9f93686b61be
Author: SeongJae Park <sj@kernel.org>
mm/damon/core: remove damon_moving_sum() and its unit test
This commit removes the damon_moving_sum() function and its associated unit
test, as the function is no longer used for any practical purpose.
> diff --git a/mm/damon/core.c b/mm/damon/core.c
> index a41b66b26a472..670cbfdf880ce 100644
> --- a/mm/damon/core.c
> +++ b/mm/damon/core.c
[ ... ]
> -static unsigned int damon_moving_sum(unsigned int mvsum, unsigned int nomvsum,
> - unsigned int len_window, unsigned int new_value)
> -{
> - return mvsum - nomvsum / len_window + new_value;
> -}
> -
> /**
> * damon_update_region_access_rate() - Update the access rate of a region.
> * @r: The DAMON region to update for its access check result.
[Severity: Low]
Are we able to drop the attrs parameter from this function now?
Following the removal of damon_moving_sum(), the attrs parameter is no longer
used in the body of damon_update_region_access_rate():
mm/damon/core.c:damon_update_region_access_rate() {
if (accessed)
r->nr_accesses++;
}
Would it make sense to remove the attrs parameter from the prototype in
include/linux/damon.h and from this function definition?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260620172244.90953-1-sj@kernel.org?part=12
next prev parent reply other threads:[~2026-06-20 17:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-20 17:22 [RFC PATCH v1.1 00/13] mm/damon: optimize out nr_accesses_bp SeongJae Park
2026-06-20 17:22 ` [RFC PATCH v1.1 01/13] mm/damon: introduce damon_nr_accesses_mvsum() SeongJae Park
2026-06-20 17:36 ` sashiko-bot
2026-06-20 17:39 ` SeongJae Park
2026-06-20 17:41 ` SeongJae Park
2026-06-20 17:22 ` [RFC PATCH v1.1 02/13] mm/damon/tests/core-kunit: test damon_mvsum() SeongJae Park
2026-06-20 17:22 ` [RFC PATCH v1.1 03/13] mm/damon/core: use damon_nr_accesses_mvsum() in __damos_valid_target() SeongJae Park
2026-06-20 17:41 ` sashiko-bot
2026-06-20 18:07 ` SeongJae Park
2026-06-20 17:22 ` [RFC PATCH v1.1 04/13] mm/damon/core: use damon_nr_accesses_mvsum() for damos region tracing SeongJae Park
2026-06-20 17:22 ` [RFC PATCH v1.1 05/13] mm/damon/sysfs-schemes: use damon_nr_accesses_mvsum() for damo regions SeongJae Park
2026-06-20 17:37 ` sashiko-bot
2026-06-20 18:19 ` SeongJae Park
2026-06-20 17:22 ` [RFC PATCH v1.1 06/13] mm/damon/core: remove damon_warn_fix_nr_accesses_corruption() SeongJae Park
2026-06-20 17:22 ` [RFC PATCH v1.1 07/13] mm/damon/core: remove damon_verify_reset_aggregated() SeongJae Park
2026-06-20 17:22 ` [RFC PATCH v1.1 08/13] mm/damon/core: remove damon_verify_merge_regions_of() SeongJae Park
2026-06-20 17:22 ` [RFC PATCH v1.1 09/13] mm/damon/tests/core-kunit: remove nr_accesses_bp setup and tests SeongJae Park
2026-06-20 17:22 ` [RFC PATCH v1.1 10/13] selftests/damon/drgn_dump_damon_status: do not dump nr_accesses_bp SeongJae Park
2026-06-20 17:22 ` [RFC PATCH v1.1 11/13] mm/damon/core: remove nr_accesses_bp setups and updates SeongJae Park
2026-06-20 17:34 ` sashiko-bot
2026-06-20 17:45 ` SeongJae Park
2026-06-20 18:20 ` SeongJae Park
2026-06-20 17:22 ` [RFC PATCH v1.1 12/13] mm/damon/core: remove damon_moving_sum() and its unit test SeongJae Park
2026-06-20 17:35 ` sashiko-bot [this message]
2026-06-20 17:47 ` SeongJae Park
2026-06-20 17:22 ` [RFC PATCH v1.1 13/13] mm/damon: remove damon_region->nr_accesses_bp SeongJae Park
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=20260620173547.0F18E1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=damon@lists.linux.dev \
--cc=sashiko-reviews@lists.linux.dev \
--cc=sj@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