mm-damon-remove-damon_callback-after_sampling.patch removed from -mm tree
The quilt patch titled
Subject: mm/damon: remove damon_callback->after_sampling
has been removed from the -mm tree. Its filename was
mm-damon-remove-damon_callback-after_sampling.patch
This patch was dropped because it was merged into the mm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: SeongJae Park <[email protected]>
Subject: mm/damon: remove damon_callback->after_sampling
Date: Thu, 6 Mar 2025 09:59:06 -0800
The callback was used by DAMON sysfs interface for reading DAMON internal data. But it is no more being used, and damon_call() can do similar works in a better way. Remove it.
Signed-off-by SeongJae Park <[email protected]>
Signed-off-by Andrew Morton <[email protected]>
---
include/linux/damon.h | 11 ++++------- mm/damon/core.c | 3 --- 2 files changed, 4 insertions(+), 10 deletions(-)
include/linux/damon.h renamed from include/linux/damon.h~mm-damon-remove-damon_callback-after_sampling +4 -7
@@ -604,7 +604,6 @@ struct damon_operations {* struct damon_callback - Monitoring events notification callbacks. * * @after_wmarks_check: Called after each schemes' watermarks check. -* @after_sampling: Called after each sampling. * @after_aggregation: Called after each aggregation. * @before_damos_apply: Called before applying DAMOS action. * @before_terminate: Called before terminating the monitoring.
@@ -617,17 +616,15 @@ struct damon_operations {* attributes of the monitoring context while it's deactivated due to the * watermarks, this is the good place to do. * -* The monitoring thread calls @after_sampling and @after_aggregation for each -* of the sampling intervals and aggregation intervals, respectively. -* Therefore, users can safely access the monitoring results without additional -* protection. For the reason, users are recommended to use these callback for -* the accesses to the results. +* The monitoring thread calls @after_aggregation for each of the aggregation +* intervals. Therefore, users can safely access the monitoring results +* without additional protection. For the reason, users are recommended to use +* these callback for the accesses to the results. * * If any callback returns non-zero, monitoring stops. */ struct damon_callback {int (*after_wmarks_check)(struct damon_ctx *context); -int (*after_sampling)(struct damon_ctx *context);int (*after_aggregation)(struct damon_ctx *context); int (*before_damos_apply)(struct damon_ctx *context, struct damon_target *target,
mm/damon/core.c renamed from mm/damon/core.c~mm-damon-remove-damon_callback-after_sampling +0 -3
@@ -2432,9 +2432,6 @@ static int kdamond_fn(void *data)if (ctx->ops.prepare_access_checks) ctx->ops.prepare_access_checks (ctx); -if (ctx->callback.after_sampling && - ctx->callback.after_sampling (ctx)) -break ;kdamond_usleep (sample_interval); ctx->passed_sample_intervals++;
_
Patches currently in -mm which might be from [email protected] are