Re: (sashiko review) [RFC PATCH] mm/damon/core: avoid time-quota permanently disabling scheme

[SeongJae Park]

TL; DR: sashiko found no issue in this patch.  I will repost this patch after
dropping RFC, soon.

Forwarding sashiko review in a reply format with my inline
comments below, for details of my view and doing discussions
via mails if needed.

> # review url: https://sashiko.dev/#/patchset/20260405225440.76827-1-sj@xxxxxxxxxx
> # start of sashiko.dev inline review
> commit 93dc55170095d9a174cb626df2cde4fe5e49b9a6
> Author: SeongJae Park <sj@xxxxxxxxxx>
> 
> mm/damon/core: avoid time-quota permanently disabling scheme
> 
> When a DAMOS scheme throughput is very slow, the time quota can make the
> effective size quota smaller than the minimum region size. This causes
> the action to be skipped, freezing the effective size quota updates.
> This patch sets the time quota-modified effective size quota to be at
> least min_region_sz.
> 
> Link: https://lore.kernel.org/20260405192504.110014-1-sj@xxxxxxxxxx
> 
> > diff --git a/mm/damon/core.c b/mm/damon/core.c
> > index 3bc7a2bbfe7de..12544c60531d3 100644
> > --- a/mm/damon/core.c
> > +++ b/mm/damon/core.c
> 
> [ ... ]
> 
> > @@ -2409,6 +2410,7 @@ static void damos_set_effective_quota(struct damos_quota *quota)
> >  		else
> >  			throughput = PAGE_SIZE * 1024;
> >  		esz = min(throughput * quota->ms, esz);
> > +		esz = max(ctx->min_region_sz, esz);
> 
> Does this minimum region size bound incorrectly override DAMOS quota goals?
> 
> In damos_set_effective_quota(), esz is first initialized based on
> quota->goals. The goal tuner can legitimately reduce esz below
> ctx->min_region_sz (for example, to 0) to completely pause the scheme if
> the system is over-achieving its target limits.
> 
> Because the max() operates on the combined esz instead of just the time
> quota component, it artificially inflates the quota back up to
> ctx->min_region_sz. This forces the scheme to process at least one region
> per charge window, overriding the goal tuner's request to pause the scheme.
> 
> If quota->ms is 0, this block is bypassed and the goal is properly
> respected, leading to inconsistent behavior depending on whether a time
> quota is configured.

That's correct, and it is an intended behavior.

It's true that it is bit inconsistent.  But I don't think that will cause any
real issue, since the difference is quite minimal (min_region_sz quota).

> 
> Could the lower bound be applied exclusively to the calculated time quota
> before it is combined with the goal-based quota?
> 
> For example:
> 
> unsigned long time_esz = max(throughput * quota->ms, ctx->min_region_sz);
> esz = min(time_esz, esz);

Maybe we can later improve the behavior by doing the time quota based esz setup
before goals based setup.  But that's not good for stable kernels hotfix in my
opinion, so it is out of the scope of this patch.

> 
> 
> # end of sashiko.dev inline review
> # review url: https://sashiko.dev/#/patchset/20260405225440.76827-1-sj@xxxxxxxxxx


Thanks,
SJ

# hkml [1] generated a draft of this mail.  You can regenerate
# this using below command:
#
#     hkml patch sashiko_dev --for_forwarding \
#             20260405225440.76827-1-sj@xxxxxxxxxx
#
# [1] https://github.com/sjp38/hackermail