From: Zenghui Yu <zenghui.yu@linux.dev>
To: linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: hannes@cmpxchg.org, yosry@kernel.org, nphamcs@gmail.com,
chengming.zhou@linux.dev, tj@kernel.org, mkoutny@suse.com,
Shuah Khan <shuah@kernel.org>,
mhocko@kernel.org, Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeel.butt@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>
Subject: cgroup/test_zswap failed with "zswpout does not increase after test program"
Date: Tue, 7 Jul 2026 17:38:13 +0800 [thread overview]
Message-ID: <c0970cee-42c2-4844-b88e-229853f08e90@linux.dev> (raw)
Hi,
Running cgroup/test_zswap on my arm64 box failed immediately with:
[root@localhost cgroup]# ./test_zswap
TAP version 13
1..8
# zswpout does not increase after test program
not ok 1 test_zswap_usage
[...]
I'm sure that pages are successfully written into zswap by checking the
count_memcg_events(.., idx=ZSWPOUT, ..) trace events. But "zswpout_after"
in test_zswap_usage() is 0 and results in this failure.
I guess the problem is that (in this particular case) the memcg stats has
not been flushed when userspace reads it.
memcg_stat_format()
mem_cgroup_flush_stats()
__mem_cgroup_flush_stats(.., force=false)
needs_flush = memcg_vmstats_needs_flush();
static bool memcg_vmstats_needs_flush(struct memcg_vmstats *vmstats)
{
return atomic_long_read(&vmstats->stats_updates) >
MEMCG_CHARGE_BATCH * num_online_cpus();
}
I can image that memcg_vmstats_needs_flush() will return false because I'm
testing a 16k-page-size kernel on a box with 96 cpus..
As we have a periodic flusher flushed all the stats every 2 seconds, I use
the following diff to wait the flusher to expose the accurate stats to
userspace.
diff --git a/tools/testing/selftests/cgroup/lib/cgroup_util.c b/tools/testing/selftests/cgroup/lib/cgroup_util.c
index 3ce134509041..9596f294da0b 100644
--- a/tools/testing/selftests/cgroup/lib/cgroup_util.c
+++ b/tools/testing/selftests/cgroup/lib/cgroup_util.c
@@ -95,6 +95,8 @@ int cg_read(const char *cgroup, const char *control, char *buf, size_t len)
snprintf(path, sizeof(path), "%s/%s", cgroup, control);
+ sleep(2);
+
ret = read_text(path, buf, len);
return ret >= 0 ? 0 : ret;
}
I have no idea how to "fix" it properly. Please have a look!
Thanks,
Zenghui
next reply other threads:[~2026-07-07 9:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 9:38 Zenghui Yu [this message]
2026-07-07 12:01 ` cgroup/test_zswap failed with "zswpout does not increase after test program" Michal Koutný
2026-07-07 12:14 ` Zenghui Yu
2026-07-07 18:25 ` Yosry Ahmed
2026-07-07 21:35 ` Nhat Pham
2026-07-07 21:36 ` Yosry Ahmed
2026-07-07 21:46 ` Nhat Pham
2026-07-07 21:49 ` Yosry Ahmed
2026-07-08 19:00 ` Michal Koutný
2026-07-08 19:08 ` Yosry Ahmed
2026-07-10 17:30 ` Nhat Pham
2026-07-10 18:25 ` Yosry Ahmed
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=c0970cee-42c2-4844-b88e-229853f08e90@linux.dev \
--to=zenghui.yu@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=chengming.zhou@linux.dev \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mkoutny@suse.com \
--cc=muchun.song@linux.dev \
--cc=nphamcs@gmail.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=shuah@kernel.org \
--cc=tj@kernel.org \
--cc=yosry@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 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.