From: SeongJae Park <sj@kernel.org>
To: Hailong Tu <tuhailong@gmail.com>
Cc: akpm@linux-foundation.org, sj@kernel.org,
torvalds@linux-foundation.org, gregkh@google.com,
surenb@google.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, willy@infradead.org,
tuhailong@oppo.com, lichunpeng@oppo.com, aaron.qiu@oppo.com,
fanguoze@oppo.com
Subject: Re: [PATCH v3] mm/damon: Fix the timer always stays active
Date: Thu, 21 Apr 2022 08:48:06 +0000 [thread overview]
Message-ID: <20220421084806.72553-1-sj@kernel.org> (raw)
In-Reply-To: <20220421010640.383365-1-tuhailong@gmail.com>
Hi Hailong,
On Thu, 21 Apr 2022 09:06:41 +0800 Hailong Tu <tuhailong@gmail.com> wrote:
> The timer stays active even if the reclaim mechanism is never enabled.
I'd like to make it clear that this change is for DAMON_RECLAIM by making the
first part of the subject 'mm/damon/reclaim:', and adjusting above sentence.
> It is unnecessary overhead can be completely avoided by using module_param_call() for enabled flag.
Let's wrap the line at 75 columns
(https://docs.kernel.org/process/submitting-patches.html#the-canonical-patch-format).
>
> Signed-off-by: Hailong Tu <tuhailong@gmail.com>
> ---
> mm/damon/reclaim.c | 19 +++++++++++++++++--
> 1 file changed, 17 insertions(+), 2 deletions(-)
>
> diff --git a/mm/damon/reclaim.c b/mm/damon/reclaim.c
> index e34c4d0c4d93..46505c501cd6 100644
> --- a/mm/damon/reclaim.c
> +++ b/mm/damon/reclaim.c
> @@ -28,7 +28,6 @@
> * this.
> */
> static bool enabled __read_mostly;
> -module_param(enabled, bool, 0600);
>
> /*
> * Time threshold for cold memory regions identification in microseconds.
> @@ -358,11 +357,27 @@ static void damon_reclaim_timer_fn(struct work_struct *work)
> enabled = last_enabled;
> }
>
> - schedule_delayed_work(&damon_reclaim_timer,
> + if (enabled)
> + schedule_delayed_work(&damon_reclaim_timer,
> msecs_to_jiffies(ENABLE_CHECK_INTERVAL_MS));
> }
> static DECLARE_DELAYED_WORK(damon_reclaim_timer, damon_reclaim_timer_fn);
>
> +static int enabled_store(const char *val,
> + const struct kernel_param *kp)
> +{
> + int rc = param_set_bool(val, kp);
> +
> + if (rc < 0)
> + return rc;
> +
> + if (enabled)
> + schedule_delayed_work(&damon_reclaim_timer, 0);
> +
> + return 0;
> +}
> +module_param_call(enabled, enabled_store, param_get_bool, &enabled, 0600);
module_param_call() is commented as obsolete. Could we use module_param_cb()
instead as suggested by the comment?
> +
> static int damon_reclaim_after_aggregation(struct damon_ctx *c)
> {
> struct damos *s;
> --
> 2.25.1
>
Thanks,
SJ
prev parent reply other threads:[~2022-04-21 8:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 1:06 Hailong Tu
2022-04-21 8:48 ` SeongJae 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=20220421084806.72553-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=aaron.qiu@oppo.com \
--cc=akpm@linux-foundation.org \
--cc=fanguoze@oppo.com \
--cc=gregkh@google.com \
--cc=lichunpeng@oppo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=surenb@google.com \
--cc=torvalds@linux-foundation.org \
--cc=tuhailong@gmail.com \
--cc=tuhailong@oppo.com \
--cc=willy@infradead.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