From: Nhat Pham <nphamcs@gmail.com>
To: Li Wang <liwang@redhat.com>
Cc: akpm@linux-foundation.org, rppt@kernel.org, david@kernel.org,
hannes@cmpxchg.org, yosry@kernel.org, ljs@kernel.org,
Liam.Howlett@oracle.com, mhocko@suse.com, shuah@kernel.org,
chengming.zhou@linux.dev, longman@redhat.com, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
cgroups@vger.kernel.org, "Michal Hocko" <mhocko@kernel.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Muchun Song" <muchun.song@linux.dev>,
"Tejun Heo" <tj@kernel.org>,
"Roman Gushchin" <roman.gushchin@linux.dev>,
"Shakeel Butt" <shakeel.butt@linux.dev>,
"Yosry Ahmed" <yosryahmed@google.com>
Subject: Re: [PATCH v6 6/8] selftest/cgroup: fix zswap test_no_invasive_cgroup_shrink on large pagesize system
Date: Sun, 12 Apr 2026 17:29:35 -0700 [thread overview]
Message-ID: <CAKEwX=M150Hw0Ncs69SCWRr7J+vK5F0biotkz=MSFvFG3rgjow@mail.gmail.com> (raw)
In-Reply-To: <20260402063714.55124-7-liwang@redhat.com>
On Wed, Apr 1, 2026 at 11:38 PM Li Wang <liwang@redhat.com> wrote:
>
> test_no_invasive_cgroup_shrink sets up two cgroups: wb_group, which is
> expected to trigger zswap writeback, and a control group (renamed to
> zw_group), which should only have pages sitting in zswap without any
> writeback.
>
> There are two problems with the current test:
>
> 1) The data patterns are reversed. wb_group uses allocate_bytes(), which
> writes only a single byte per page — trivially compressible,
> especially by zstd — so compressed pages fit within zswap.max and
> writeback is never triggered. Meanwhile, the control group uses
> getrandom() to produce hard-to-compress data, but it is the group
> that does *not* need writeback.
>
> 2) The test uses fixed sizes (10K zswap.max, 10MB allocation) that are
> too small on systems with large PAGE_SIZE (e.g. 64K), failing to
> build enough memory pressure to trigger writeback reliably.
>
> Fix both issues by:
> - Swapping the data patterns: fill wb_group pages with partially
> random data (getrandom for page_size/4 bytes) to resist compression
> and trigger writeback, and fill zw_group pages with simple repeated
> data to stay compressed in zswap.
> - Making all size parameters PAGE_SIZE-aware: set allocation size to
> PAGE_SIZE * 1024, memory.zswap.max to PAGE_SIZE, and memory.max to
> allocation_size / 2 for both cgroups.
> - Allocating memory inline instead of via cg_run() so the pages
> remain resident throughout the test.
>
> === Error Log ===
> # getconf PAGESIZE
> 65536
>
> # ./test_zswap
> TAP version 13
> ...
> ok 5 test_zswap_writeback_disabled
> ok 6 # SKIP test_no_kmem_bypass
> not ok 7 test_no_invasive_cgroup_shrink
I assume the test passed after fix? ;)
>
> Signed-off-by: Li Wang <liwang@redhat.com>
> Cc: Johannes Weiner <hannes@cmpxchg.org>
> Cc: Michal Hocko <mhocko@kernel.org>
> Cc: Michal Koutný <mkoutny@suse.com>
> Cc: Muchun Song <muchun.song@linux.dev>
> Cc: Nhat Pham <nphamcs@gmail.com>
> Cc: Tejun Heo <tj@kernel.org>
> Cc: Roman Gushchin <roman.gushchin@linux.dev>
> Cc: Shakeel Butt <shakeel.butt@linux.dev>
> Cc: Yosry Ahmed <yosryahmed@google.com>
> ---
>
> Notes:
> v5:
> - Swap data patterns: use getrandom() for wb_group and simple
> memset for zw_group to fix the reversed allocation logic.
> - Rename control_group to zw_group for clarity.
> - Allocate memory inline instead of via cg_run() so pages remain
> resident throughout the test.
>
> tools/testing/selftests/cgroup/test_zswap.c | 70 ++++++++++++++-------
> 1 file changed, 49 insertions(+), 21 deletions(-)
LGTM. Thanks for fixing the tests :)
Acked-by: Nhat Pham <nphamcs@gmail.com>
next prev parent reply other threads:[~2026-04-13 0:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 6:37 [PATCH v6 0/8] selftests/cgroup: improve zswap tests robustness and support large page sizes Li Wang
2026-04-02 6:37 ` [PATCH v6 1/8] selftests/cgroup: skip test_zswap if zswap is globally disabled Li Wang
2026-04-02 6:37 ` [PATCH v6 2/8] selftests/cgroup: avoid OOM in test_swapin_nozswap Li Wang
2026-04-02 6:37 ` [PATCH v6 3/8] selftests/cgroup: use runtime page size for zswpin check Li Wang
2026-04-02 6:37 ` [PATCH v6 4/8] selftests/cgroup: rename PAGE_SIZE to BUF_SIZE in cgroup_util Li Wang
2026-04-02 6:37 ` [PATCH v6 5/8] selftests/cgroup: replace hardcoded page size values in test_zswap Li Wang
2026-04-03 17:16 ` Nhat Pham
2026-04-02 6:37 ` [PATCH v6 6/8] selftest/cgroup: fix zswap test_no_invasive_cgroup_shrink on large pagesize system Li Wang
2026-04-13 0:29 ` Nhat Pham [this message]
2026-04-02 6:37 ` [PATCH v6 7/8] selftest/cgroup: fix zswap attempt_writeback() on 64K " Li Wang
2026-04-13 0:15 ` Nhat Pham
2026-04-02 6:37 ` [PATCH v6 8/8] selftests/cgroup: test_zswap: wait for asynchronous writeback Li Wang
2026-04-13 0:01 ` Nhat Pham
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='CAKEwX=M150Hw0Ncs69SCWRr7J+vK5F0biotkz=MSFvFG3rgjow@mail.gmail.com' \
--to=nphamcs@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=chengming.zhou@linux.dev \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwang@redhat.com \
--cc=ljs@kernel.org \
--cc=longman@redhat.com \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--cc=mkoutny@suse.com \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=rppt@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=shuah@kernel.org \
--cc=tj@kernel.org \
--cc=yosry@kernel.org \
--cc=yosryahmed@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox