@@ -348,7 +348,8 @@ enum damos_filter_type {
/**
* struct damos_filter - DAMOS action target memory filter.
* @type: Type of the target memory.
- * @matching: If the @type-matching memory should be filtered out.
+ * @matching: Whether this is for @type-matching memory.
+ * @pass: Whether the memory should pass-through the filter.
* @memcg_id: Memcg id of the question if @type is DAMOS_FILTER_MEMCG.
* @addr_range: Address range if @type is DAMOS_FILTER_TYPE_ADDR.
* @target_idx: Index of the &struct damon_target of
@@ -365,6 +366,7 @@ enum damos_filter_type {
struct damos_filter {
enum damos_filter_type type;
bool matching;
+ bool pass;
union {
unsigned short memcg_id;
struct damon_addr_range addr_range;
@@ -275,6 +275,7 @@ struct damos_filter *damos_new_filter(enum damos_filter_type type,
return NULL;
filter->type = type;
filter->matching = matching;
+ filter->pass = false;
INIT_LIST_HEAD(&filter->list);
return filter;
}
DAMOS filters work as only exclusive (block) filters. This makes it easy to be confused, and restrictive at combining multiple filters for various types of memory. To extend DAMOS filters for inclusion behavior, add a filed to damos_filter. Following commits will make the field to decide whether the filter should work as an exclusive (block) filter, or an inclusive (pass) filter. Signed-off-by: SeongJae Park <sj@kernel.org> --- include/linux/damon.h | 4 +++- mm/damon/core.c | 1 + 2 files changed, 4 insertions(+), 1 deletion(-)