From: SeongJae Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>, Shuah Khan <shuah@kernel.org>,
damon@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-mm@kvack.org
Subject: [PATCH 0/5] selftests/damon: improve leak detection and wss estimation reliability
Date: Fri, 16 Jan 2026 18:07:23 -0800 [thread overview]
Message-ID: <20260117020731.226785-1-sj@kernel.org> (raw)
Two DAMON selftets, namely 'sysfs_memcg_leak' and
'sysfs_update_schemes_tried_regions_wss_estimation' frequently show
intermittent failures due to their unreliable leak detection and working
set size estimation. Make those more reliable.
SeongJae Park (5):
selftests/damon/sysfs_memcg_path_leak.sh: use kmemleak
selftests/damon/wss_estimation: test for up to 160 MiB working set
size
selftests/damon/access_memory: add repeat mode
selftests/damon/wss_estimation: ensure number of collected wss
selftests/damon/wss_estimation: deduplicate failed samples output
tools/testing/selftests/damon/access_memory.c | 29 +++++++++----
.../selftests/damon/sysfs_memcg_path_leak.sh | 26 ++++++------
...te_schemes_tried_regions_wss_estimation.py | 41 +++++++++++++++----
3 files changed, 67 insertions(+), 29 deletions(-)
base-commit: 3944e89e2ad1bafac43daae60b56d2847227ab01
--
2.47.3
next reply other threads:[~2026-01-17 2:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-17 2:07 SeongJae Park [this message]
2026-01-17 2:07 ` [PATCH 1/5] selftests/damon/sysfs_memcg_path_leak.sh: use kmemleak SeongJae Park
2026-01-17 2:07 ` [PATCH 2/5] selftests/damon/wss_estimation: test for up to 160 MiB working set size SeongJae Park
2026-01-17 2:07 ` [PATCH 3/5] selftests/damon/access_memory: add repeat mode SeongJae Park
2026-01-17 2:07 ` [PATCH 4/5] selftests/damon/wss_estimation: ensure number of collected wss SeongJae Park
2026-01-17 2:07 ` [PATCH 5/5] selftests/damon/wss_estimation: deduplicate failed samples output 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=20260117020731.226785-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-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuah@kernel.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