From: SeongJae Park <sj@kernel.org>
Cc: SeongJae Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
honggyu.kim@sk.com, hyeongtak.ji@sk.com, kernel_team@skhynix.com,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: [RFC PATCH 0/3] mm/damon: add a DAMOS filter type for page granularity access recheck
Date: Wed, 6 Mar 2024 19:00:10 -0800 [thread overview]
Message-ID: <20240307030013.47041-1-sj@kernel.org> (raw)
DAMON allows users to specify desired ranges of overhead and accuracy of
the monitoring, and do its best effort to make most lightweight and
accurate results. A recent discussion for tiered memory management
support from DAMON[1] revealed that the best effort accuracy may not
suffice in some use cases, while increasing the minimum accuracy can
incur too high overhead. The discussion further concluded finding
memory regions of specific access pattern via DAMON first, and then
double checking the access of the region again in finer granularity
could help increasing the accuracy while keeping the low overhead.
Add a new type of DAMOS filter, namely YOUNG for such a case. Like anon
and memcg, the type of filter is applied to each page of the memory
region of DAMOS target memory region, and check if the page is accessed
since the last check. Because this is a filter type that applied in
page granularity, the support depends on DAMON operations set. Because
there are expected usages of this filter for physical address space
based DAMOS usage[1], implement the support for only DAMON operations
set for the physical address space, paddr.
[1] https://lore.kernel.org/r/20240227235121.153277-1-sj@kernel.org
SeongJae Park (3):
mm/damon: add DAMOS filter type YOUNG
mm/damon/paddr: implement damon_folio_young()
mm/damon/paddr: support DAMOS filter type YOUNG
include/linux/damon.h | 2 ++
mm/damon/paddr.c | 29 +++++++++++++++++++----------
mm/damon/sysfs-schemes.c | 1 +
3 files changed, 22 insertions(+), 10 deletions(-)
base-commit: 78a854de1f605e99ccc20df1775f237120cca47c
--
2.39.2
next reply other threads:[~2024-03-07 3:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 3:00 SeongJae Park [this message]
2024-03-07 3:00 ` [RFC PATCH 1/3] mm/damon: add DAMOS filter type YOUNG SeongJae Park
2024-03-07 3:00 ` [RFC PATCH 2/3] mm/damon/paddr: implement damon_folio_young() SeongJae Park
2024-03-07 3:00 ` [RFC PATCH 3/3] mm/damon/paddr: support DAMOS filter type YOUNG SeongJae Park
2024-03-09 1:53 ` 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=20240307030013.47041-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=honggyu.kim@sk.com \
--cc=hyeongtak.ji@sk.com \
--cc=kernel_team@skhynix.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).