OpenVZ / Virtuozzo kernel development (devel@openvz.org)
 help / color / mirror / Atom feed
From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>,
	Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 0/3] mm/memcontrol: tidy up the memory.numa_migrate code
Date: Thu, 12 Nov 2026 19:04:53 +0100	[thread overview]
Message-ID: <d332bf39-fcdc-4881-8813-cd36ff965208@virtuozzo.com> (raw)
In-Reply-To: <20261028-b4-prep-khorenko-vstor-152197-numa-migrate-cleanup-v1-0-aa959eecd3fd@virtuozzo.com>

a kind ping :)

--
Best regards,

Konstantin Khorenko,
Virtuozzo Linux Kernel Team

On 10/28/26 14:49, Konstantin Khorenko wrote:
> Leftovers found while fixing VSTOR-151607, where the allocator of
> memory.numa_migrate had fallen behind the upstream function it was
> copied from. Nothing here changes behaviour. Applies on top of
> "mm/memcontrol: numa_migrate destinations of the source folio order".
> 
> - 1: update_lru_sizes() lost its only caller when the isolation loop
>   switched to lruvec_del_folio(); static __always_inline, so no
>   warning ever came.
> - 2: the comment in the isolation loop told the rebase history of the
>   code. It now names the upstream functions the loop and the allocator
>   copy (isolate_migratepages_block(), isolate_lru_folios(),
>   alloc_migration_target()), which is what the next rebase has to
>   compare against. The commented-out conditions and the pre-folio name
>   of the allocator go with it.
> - 3: the MAX_SCAN argument of memory.numa_migrate is documented in
>   pages while the scan counts folios.
> 
> https://virtuozzo.atlassian.net/browse/VSTOR-152197
> 
> Assisted-by: LLM
> Signed-off-by: Konstantin Khorenko <khorenko@virtuozzo.com>
> ---
> Konstantin Khorenko (3):
>       mm/memcontrol: drop the unused update_lru_sizes()
>       mm/memcontrol: say where the numa_migrate code comes from
>       mm/memcontrol: memory.numa_migrate MAX_SCAN counts folios
> 
>  mm/memcontrol.c | 54 +++++++++++++-----------------------------------------
>  1 file changed, 13 insertions(+), 41 deletions(-)
> ---
> base-commit: 8f4b2db111bee113348656f1b1f98c841d7c19e7
> change-id: 20261028-b4-prep-khorenko-vstor-152197-numa-migrate-cleanup-dcc488d8d106
> 
> Best regards,
> --  
> Konstantin Khorenko,
> Virtuozzo Linux Kernel Team
> 

_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

      parent reply	other threads:[~2026-11-12 18:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 13:49 Konstantin Khorenko
2026-10-28 13:49 ` [Devel] [PATCH hci-8.1 1/3] mm/memcontrol: drop the unused update_lru_sizes() Konstantin Khorenko
2026-11-17  8:40   ` Pavel Tikhomirov
2026-10-28 13:49 ` [Devel] [PATCH hci-8.1 2/3] mm/memcontrol: say where the numa_migrate code comes from Konstantin Khorenko
2026-11-17  8:40   ` Pavel Tikhomirov
2026-10-28 13:49 ` [Devel] [PATCH hci-8.1 3/3] mm/memcontrol: memory.numa_migrate MAX_SCAN counts folios Konstantin Khorenko
2026-11-17  8:40   ` Pavel Tikhomirov
2026-11-12 18:04 ` 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=d332bf39-fcdc-4881-8813-cd36ff965208@virtuozzo.com \
    --to=khorenko@virtuozzo.com \
    --cc=devel@openvz.org \
    --cc=ptikhomirov@virtuozzo.com \
    --cc=vasileios.almpanis@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