From: Liew Rui Yan <aethernet65535@gmail.com>
To: sj@kernel.org
Cc: aethernet65535@gmail.com, damon@lists.linux.dev, linux-mm@kvack.org
Subject: Re: [RFC PATCH v6] mm/damon: add synchronous commit for commit_inputs
Date: Sat, 28 Mar 2026 12:03:39 +0800 [thread overview]
Message-ID: <20260328040339.51871-1-aethernet65535@gmail.com> (raw)
In-Reply-To: <20260327135939.4085-1-sj@kernel.org>
> > +static int damon_lru_sort_commit_inputs_store(const char *val,
> > + const struct kernel_param *kp)
> > +{
> > + bool commit_inputs_request;
> > int err;
> > + struct damon_call_control control = {
> > + .fn = damon_lru_sort_commit_inputs_fn,
> > + .repeat = false,
>
> Undeclared fields are initialized to zero. I don't think we need to explicitly
> set repeat here.
Agreed. This change can makes the code more clean.
> > + return control.return_code;
>
> Shouldn't we return err if it is not zero?
Correct, I've noticed that as well [1]. But thank you for reminding me
anyway.
> > --- a/mm/damon/reclaim.c
> > +++ b/mm/damon/reclaim.c
>
> Same comments can be applied to changes for this file.
I will apply these changes in the next version. I will remove the RFC
tag because I believe the high-level design in now solid, and the
low-level details have been mostly addressed. :>
[1] https://lore.kernel.org/20260327071410.73642-1-aethernet65535@gmail.com
Best regards,
Rui Yan
prev parent reply other threads:[~2026-03-28 4:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 6:25 [RFC PATCH v6] mm/damon: add synchronous commit for commit_inputs Liew Rui Yan
2026-03-27 7:04 ` (sashiko review) " Liew Rui Yan
2026-03-27 7:14 ` Liew Rui Yan
2026-03-28 4:02 ` Liew Rui Yan
2026-03-27 13:59 ` SeongJae Park
2026-03-28 4:03 ` Liew Rui Yan [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=20260328040339.51871-1-aethernet65535@gmail.com \
--to=aethernet65535@gmail.com \
--cc=damon@lists.linux.dev \
--cc=linux-mm@kvack.org \
--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