From: no-reply@sashiko.virtuozzo.com
To: khorenko@virtuozzo.com, Eva Kurchatova <eva.kurchatova@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 2/3] selftests: cgroup: mark the pages cold before numa_migrate starts
Date: Fri, 13 Nov 2026 04:27:55 +0000 [thread overview]
Message-ID: <010701a1d32981a2-7a0916d2-d2f8-430f-a06e-a7240ffa50e2-000000@eu-central-1.amazonses.com> (raw)
In-Reply-To: <20261113042331.517488-3-eva.kurchatova@virtuozzo.com>
> The inactive variants of test_numa_migrate report their pages populated
> before they madvise(MADV_COLD) them. The parent starts the migration as
> soon as 85% of the pages are inactive on the source node, while the
> rest are still being deactivated. memory.numa_migrate takes the size of
> each LRU list as its scan budget when it gets to the list, so the pages
> that become inactive later are not scanned, and up to the 15% that
> verify_stats() tolerates can stay behind. The slower a kernel
> deactivates the pages, the more often the test fails, which made
> inactive_disk_file fail often on coverage kernels.
>
> Call madvise(MADV_COLD) before reporting the pages populated.
>
> Fixes: 3842964f4497 ("selftests: cgroup: test numa migration of lruvecs")
> https://virtuozzo.atlassian.net/browse/VSTOR-154520
> Feature: fix selftests
>
> Signed-off-by: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.vzint.dev/#/patchset/20261113042331.517488-1-eva.kurchatova@virtuozzo.com?part=2
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next prev parent reply other threads:[~2026-11-13 4:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 4:19 [Devel] [PATCH hci-8.1 0/3] selftests: cgroup: fix test_numa_migrate, inactive_disk_file Eva Kurchatova
2026-11-13 4:19 ` [Devel] [PATCH hci-8.1 1/3] selftests: harness: run the fixture teardown after a failed ASSERT Eva Kurchatova
2026-11-13 4:28 ` no-reply
2026-11-13 19:57 ` Konstantin Khorenko
2026-11-13 4:19 ` [Devel] [PATCH hci-8.1 2/3] selftests: cgroup: mark the pages cold before numa_migrate starts Eva Kurchatova
2026-11-13 4:27 ` no-reply [this message]
2026-11-13 19:57 ` Konstantin Khorenko
2026-11-13 4:20 ` [Devel] [PATCH hci-8.1 3/3] selftests: cgroup: populate the inactive file with read faults Eva Kurchatova
2026-11-13 4:28 ` no-reply
2026-11-13 19:57 ` Konstantin Khorenko
2026-11-13 19:57 ` [Devel] [PATCH hci-8.1 0/3] selftests: cgroup: fix test_numa_migrate, inactive_disk_file Konstantin Khorenko
2026-11-13 19:59 ` 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=010701a1d32981a2-7a0916d2-d2f8-430f-a06e-a7240ffa50e2-000000@eu-central-1.amazonses.com \
--to=no-reply@sashiko.virtuozzo.com \
--cc=devel@openvz.org \
--cc=eva.kurchatova@virtuozzo.com \
--cc=khorenko@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.