[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250915015807.101505-3-sj@kernel.org>
Date: Sun, 14 Sep 2025 18:58:03 -0700
From: SeongJae Park <sj@...nel.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: SeongJae Park <sj@...nel.org>,
damon@...ts.linux.dev,
kernel-team@...a.com,
linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: [PATCH 2/6] mm/damon/core: set effective quota on first charge window
The effective quota of a scheme is initialized zero, which means there
is no quota. It is set based on user-specified time/quota/quota goals.
But the later value set is done only from the second charge window. As
a result, a scheme having a user-specified quota can work as not having
the quota (unexpectedly fast) for the first charge window. In practical
and common use cases the quota interval is not too long, and the
scheme's target access pattern is restrictive. Hence the issue should
be modest. That said, it is apparently an unintended misbehavior. Fix
the problem by setting esz on the first charge window.
Fixes: 1cd243030059 ("mm/damon/schemes: implement time quota") # 5.16.x
Signed-off-by: SeongJae Park <sj@...nel.org>
---
mm/damon/core.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/mm/damon/core.c b/mm/damon/core.c
index 996647caca02..84de1cea5440 100644
--- a/mm/damon/core.c
+++ b/mm/damon/core.c
@@ -2142,8 +2142,10 @@ static void damos_adjust_quota(struct damon_ctx *c, struct damos *s)
return;
/* First charge window */
- if (!quota->total_charged_sz && !quota->charged_from)
+ if (!quota->total_charged_sz && !quota->charged_from) {
quota->charged_from = jiffies;
+ damos_set_effective_quota(quota);
+ }
/* New charge window starts */
if (time_after_eq(jiffies, quota->charged_from +
--
2.39.5
Powered by blists - more mailing lists