From: SeongJae Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>,
Yang Yingliang <yangyingliang@huawei.com>,
damon@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: [PATCH 0/5] mm/damon: support addr_unit on default monitoring targets for modules
Date: Tue, 10 Mar 2026 22:29:21 -0700 [thread overview]
Message-ID: <20260311052927.93921-1-sj@kernel.org> (raw)
DAMON_RECLAIM and DAMON_LRU_SORT support 'addr_unit' parameters only
when the monitoring target address range is explicitly set. This was
intentional for making the initial 'addr_unit' support change small.
Now 'addr_unit' support is being quite stabilized. Having the corner
case of the support is only making the code inconsistent with implicit
rules. The inconsistency makes it easy to confuse [1] readers. After
all, there is no real reason to keep 'addr_unit' support incomplete.
Add the support for the case to improve the readability and more
completely support 'addr_unit'.
This series is constructed with five patches. The first one (patch 1)
fixes a small bug that mistakenly assigns inclusive end address to open
end address, which was found from this work. The second and third ones
(patches 2 and 3) extend the default monitoring target setting functions
in the core layer one by one, to support the 'addr_unit' while making no
visible changes. The final two patches (patches 4 and 5) update
DAMON_RECLAIM and DAMON_LRU_SORT to support 'addr_unit' for the default
monitoring target address ranges, by passing the user input to the core
functions.
[1] https://lore.kernel.org/20260131015643.79158-1-sj@kernel.org
Changes from RFC
(https://lore.kernel.org/20260305053918.83786-1-sj@kernel.org)
- Rebase to latest mm-new.
- Wordsmith commit messages.
SeongJae Park (5):
mm/damon/core: fix wrong end address assignment on walk_system_ram()
mm/damon/core: support addr_unit on damon_find_biggest_system_ram()
mm/damon/core: receive addr_unit on
damon_set_region_biggest_system_ram_default()
mm/damon/reclaim: respect addr_unit on default monitoring region setup
mm/damon/lru_sort: respect addr_unit on default monitoring region
setup
include/linux/damon.h | 1 +
mm/damon/core.c | 36 +++++++++++++++++++++++++-----------
mm/damon/lru_sort.c | 7 +------
mm/damon/reclaim.c | 7 +------
mm/damon/stat.c | 2 +-
5 files changed, 29 insertions(+), 24 deletions(-)
base-commit: 31ae3f4d2741372ab511aeefc5e6898d12971fcd
--
2.47.3
next reply other threads:[~2026-03-11 5:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 5:29 SeongJae Park [this message]
2026-03-11 5:29 ` [PATCH 1/5] mm/damon/core: fix wrong end address assignment on walk_system_ram() SeongJae Park
2026-03-11 5:29 ` [PATCH 2/5] mm/damon/core: support addr_unit on damon_find_biggest_system_ram() SeongJae Park
2026-03-17 14:47 ` SeongJae Park
2026-03-11 5:29 ` [PATCH 3/5] mm/damon/core: receive addr_unit on damon_set_region_biggest_system_ram_default() SeongJae Park
2026-03-14 0:18 ` SeongJae Park
2026-03-11 5:29 ` [PATCH 4/5] mm/damon/reclaim: respect addr_unit on default monitoring region setup SeongJae Park
2026-03-11 5:29 ` [PATCH 5/5] mm/damon/lru_sort: " 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=20260311052927.93921-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 \
--cc=yangyingliang@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.