From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>,
Konstantin Khorenko <khorenko@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 v4 0/2] mm/memcontrol: numa_migrate destinations of the source folio order
Date: Thu, 29 Oct 2026 10:40:22 +0100 [thread overview]
Message-ID: <179326682217.1382434.14553239111120964870.b4-ty@b4> (raw)
In-Reply-To: <20261029-b4-prep-khorenko-vstor-151607-numa-migrate-order-v4-0-cf966bf93405@virtuozzo.com>
On Thu, 29 Oct 2026 00:17:30 +0100, Konstantin Khorenko wrote:
> mm/memcontrol: numa_migrate destinations of the source folio order
>
> memory.numa_migrate, our memcg file that vcmmd uses to move a cgroup's
> memory between NUMA nodes, allocates a 2 MB destination for every large
> folio it migrates. Page cache folios of a smaller order get a
> destination of the wrong size, and the page cache falls apart around
> it. Patch 1 is the fix, patch 2 a selftest that catches it.
>
> [...]
Applied to branch-rh10-6.12.0-211.52.1.22.x.vz10-ovz, will be released in rh10-6.12.0-211.52.1.22.12.vz10, thanks!
[1/2] mm/memcontrol: allocate numa_migrate targets of the source folio order
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/a804befd5e7f
[2/2] selftests/ve: check memory.numa_migrate keeps the folio order
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/5ef9d1af4b0f
--
Konstantin Khorenko,
Virtuozzo Linux Kernel Team
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
prev parent reply other threads:[~2026-10-29 9:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 23:17 Konstantin Khorenko
2026-10-28 23:17 ` [Devel] [PATCH hci-8.1 v4 1/2] mm/memcontrol: allocate numa_migrate targets " Konstantin Khorenko
2026-10-28 23:21 ` no-reply
2026-10-28 23:17 ` [Devel] [PATCH hci-8.1 v4 2/2] selftests/ve: check memory.numa_migrate keeps the " Konstantin Khorenko
2026-10-28 23:25 ` no-reply
2026-10-29 9:40 ` Konstantin Khorenko [this message]
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=179326682217.1382434.14553239111120964870.b4-ty@b4 \
--to=khorenko@virtuozzo.com \
--cc=devel@openvz.org \
--cc=ptikhomirov@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox