From: SeongJae Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>,
damon@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: [PATCH 0/8] mm/damon: cleanup kdamond, damon_call(), damos filter and DAMON_MIN_REGION
Date: Sat, 17 Jan 2026 09:52:47 -0800 [thread overview]
Message-ID: <20260117175256.82826-1-sj@kernel.org> (raw)
Do miscellaneous code cleanups for improving readability. First three
patches cleanup kdamond termination process, by removing unused
operation set cleanup callback (patch 1) and moving damon_ctx specific
resource cleanups on kdamond termination to synchronization-easy place
(patches 2 and 3). Next two patches touch damon_call() infrastructure,
by refactoring kdamond_call() function to do less and simpler locking
operations (patch 4), and documenting when dealloc_on_free does work
(patch 5). Final three patches rename things for clear uses of those.
Those rename damos_filter_out() to be more explicit about the fact that
it is only for core-handled filters (patch 6), DAMON_MIN_REGION macro to
be more explicit it is not about number of regions but size of each
region (patch 7), and damon_ctx->min_sz_region to be different from
damos_access_patern->min_sz_region (patch 8), so that those are not
confusing and easy to grep.
SeongJae Park (8):
mm/damon: remove damon_operations->cleanup()
mm/damon/core: cleanup targets and regions at once on kdamond
termination
mm/damon/core: cancel damos_walk() before damon_ctx->kdamond reset
mm/damon/core: process damon_call_control requests on a local list
mm/damon: document damon_call_control->dealloc_on_cancel repeat
behavior
mm/damon/core: rename damos_filter_out() to damos_core_filter_out()
mm/damon: rename DAMON_MIN_REGION to DAMON_MIN_REGION_SZ
mm/damon: rename min_sz_region of damon_ctx to min_region_sz
include/linux/damon.h | 15 ++--
mm/damon/core.c | 143 +++++++++++++++--------------------
mm/damon/lru_sort.c | 4 +-
mm/damon/paddr.c | 1 -
mm/damon/reclaim.c | 4 +-
mm/damon/stat.c | 2 +-
mm/damon/sysfs.c | 11 +--
mm/damon/tests/vaddr-kunit.h | 2 +-
mm/damon/vaddr.c | 25 +++---
9 files changed, 89 insertions(+), 118 deletions(-)
base-commit: 886ef5515d08f05191b61a347fc18f371627bdd4
--
2.47.3
next reply other threads:[~2026-01-17 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-17 17:52 SeongJae Park [this message]
2026-01-17 17:52 ` [PATCH 1/8] mm/damon: remove damon_operations->cleanup() SeongJae Park
2026-01-17 17:52 ` [PATCH 2/8] mm/damon/core: cleanup targets and regions at once on kdamond termination SeongJae Park
2026-01-17 17:52 ` [PATCH 3/8] mm/damon/core: cancel damos_walk() before damon_ctx->kdamond reset SeongJae Park
2026-01-17 17:52 ` [PATCH 4/8] mm/damon/core: process damon_call_control requests on a local list SeongJae Park
2026-01-17 17:52 ` [PATCH 5/8] mm/damon: document damon_call_control->dealloc_on_cancel repeat behavior SeongJae Park
2026-01-17 17:52 ` [PATCH 6/8] mm/damon/core: rename damos_filter_out() to damos_core_filter_out() SeongJae Park
2026-01-17 17:52 ` [PATCH 7/8] mm/damon: rename DAMON_MIN_REGION to DAMON_MIN_REGION_SZ SeongJae Park
2026-01-17 17:52 ` [PATCH 8/8] mm/damon: rename min_sz_region of damon_ctx to min_region_sz SeongJae Park
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260117175256.82826-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox