DAMON development mailing list
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "SJ Park" <sj@kernel.org>
Cc: damon@lists.linux.dev
Subject: Re: [PATCH 2/3] mm/damon/core: reduce stack usage further
Date: Mon, 28 Sep 2026 08:45:19 +0000	[thread overview]
Message-ID: <20260928084519.E51841F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260928083959.4030-3-sj@kernel.org>

> From: Arnd Bergmann <arnd@arndb.de>
> 
> In a previous patch, I had annotated kdamond_tune_intervals() as
> noinline_for_stack in order to not exceed the stack frame warning
> limit. Unfortunately, my current linux-next randconfig builds show
> a similar problem again with clang-21:
> 
> mm/damon/core.c:3953:12: error: stack frame size (1288) exceeds limit (1280) in 'kdamond_fn' [-Werror,-Wframe-larger-than]
>  3953 | static int kdamond_fn(void *data)
> 
> Do the same thing with kdamond_apply_schemes(), kdamond_merge_regions(),
> and kdamond_split_regions(), which also have individually large stacks.
> This should work to keep the deepest total stack depth down much more
> as well as avoid the warning.
> 
> I also tried to reduce the complexity of kdamond_fn() itself by splitting
> out the while() loop into a separate function. While this arguably led
> to slightly more readable code, it had no effect on the total stack
> usage and just made the new function the largest stack user and had
> a nonzero risk of me getting the conversion wrong.
> 
> Fixes: 5a00cae64de1 ("mm/damon/core: reduce kernel stack usage")
> Cc: Nick Desaulniers <ndesaulniers@google.com>
> Cc: Bill Wendling <morbo@google.com>
> Cc: Justin Stitt <justinstitt@google.com>
> Cc: Ravi Jonnalagadda <ravis.opensrc@gmail.com>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Reviewed-by: SJ Park <sj@kernel.org>
> Signed-off-by: SJ Park <sj@kernel.org>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260928083959.4030-1-sj@kernel.org?part=2


  reply	other threads:[~2026-09-28  8:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28  8:39 [PATCH 0/3] mm/damon/core: cleanup code, reduce stack usage, and add kunit SJ Park
2026-09-28  8:39 ` [PATCH 1/3] mm/damon/api: remove unused NR_DAMOS_* enumerators SJ Park
2026-09-28  8:44   ` sashiko-bot
2026-09-28  8:39 ` [PATCH 2/3] mm/damon/core: reduce stack usage further SJ Park
2026-09-28  8:45   ` sashiko-bot [this message]
2026-09-28  8:39 ` [PATCH 3/3] mm/damon/tests/core-kunit: test PSI goal values with explicit samples SJ Park
2026-09-28  8:44   ` sashiko-bot

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=20260928084519.E51841F000FF@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