summaryrefslogtreecommitdiff
path: root/Documentation/devicetree/changesets.rst
diff options
context:
space:
mode:
authorSeongJae Park <sj@kernel.org>2024-10-31 11:37:57 -0700
committerAndrew Morton <akpm@linux-foundation.org>2024-11-07 14:14:58 -0800
commit8e7bde615f634a82a44b1f3d293c049fd3ef9ca9 (patch)
tree2a8d7ef5d940c86a162cc2f580264256a73b28af /Documentation/devicetree/changesets.rst
parent3488af0970445ff5532c7e8dc5e6456b877aee5e (diff)
mm/damon/core: handle zero schemes apply interval
DAMON's logics to determine if this is the time to apply damos schemes assumes next_apply_sis is always set larger than current passed_sample_intervals. And therefore assume continuously incrementing passed_sample_intervals will make it reaches to the next_apply_sis in future. The logic hence does apply the scheme and update next_apply_sis only if passed_sample_intervals is same to next_apply_sis. If Schemes apply interval is set as zero, however, next_apply_sis is set same to current passed_sample_intervals, respectively. And passed_sample_intervals is incremented before doing the next_apply_sis check. Hence, next_apply_sis becomes larger than next_apply_sis, and the logic says it is not the time to apply schemes and update next_apply_sis. In other words, DAMON stops applying schemes until passed_sample_intervals overflows. Based on the documents and the common sense, a reasonable behavior for such inputs would be applying the schemes for every sampling interval. Handle the case by removing the assumption. Link: https://lkml.kernel.org/r/20241031183757.49610-3-sj@kernel.org Fixes: 42f994b71404 ("mm/damon/core: implement scheme-specific apply interval") Signed-off-by: SeongJae Park <sj@kernel.org> Cc: <stable@vger.kernel.org> [6.7.x] Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'Documentation/devicetree/changesets.rst')
0 files changed, 0 insertions, 0 deletions