From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH vz10 1/2] ms/selftests/cgroup: skip test_zswap if zswap is globally disabled
Date: Wed, 02 Sep 2026 20:17:15 +0200 [thread overview]
Message-ID: <178837303546.1250422.14682509823164092326.b4-review@b4> (raw)
In-Reply-To: <20260831233703.1648144-1-eva.kurchatova@virtuozzo.com>
On Tue, 01 Sep 2026 02:36:54 +0300, Eva Kurchatova <eva.kurchatova@virtuozzo.com> wrote:
> Patch series "selftests/cgroup: improve zswap tests robustness and support
> large page sizes", v7.
>
> This patchset aims to fix various spurious failures and improve the
> overall robustness of the cgroup zswap selftests.
>
> The primary motivation is to make the tests compatible with architectures
> that use non-4K page sizes (such as 64K on ppc64le and arm64). Currently,
> the tests rely heavily on hardcoded 4K page sizes and fixed memory limits.
> On 64K page size systems, these hardcoded values lead to sub-page
> granularity accesses, incorrect page count calculations, and insufficient
> memory pressure to trigger zswap writeback, ultimately causing the tests
> to fail.
>
> [...]
Reviewed-by: Konstantin Khorenko <khorenko@virtuozzo.com>
--
Konstantin Khorenko <khorenko@virtuozzo.com>
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next prev parent reply other threads:[~2026-09-02 18:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 23:36 Eva Kurchatova
2026-08-31 23:36 ` [Devel] [PATCH vz10 2/2] selftests: cgroup: add a settings file with a longer timeout Eva Kurchatova
2026-09-02 18:17 ` Konstantin Khorenko
2026-09-02 18:17 ` Konstantin Khorenko [this message]
2026-09-02 18:19 ` [Devel] [PATCH vz10 1/2] ms/selftests/cgroup: skip test_zswap if zswap is globally disabled Konstantin Khorenko
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=178837303546.1250422.14682509823164092326.b4-review@b4 \
--to=khorenko@virtuozzo.com \
--cc=devel@openvz.org \
--cc=eva.kurchatova@virtuozzo.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.