All Virtuozzo development lists (kernel + QEMU)
 help / color / mirror / Atom feed
From: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
To: Konstantin Khorenko <khorenko@virtuozzo.com>
Cc: devel@openvz.org
Subject: [Devel] [PATCH hci-8.1 v2 0/2] fs/aio: fix CT migration with AIO to a node with more CPUs
Date: Mon, 16 Nov 2026 11:31:48 +0100	[thread overview]
Message-ID: <20261116-pr-ptikhomirov-vstor-154129-aio-pseudosuper-ring-v2-0-532d149b4bd7@virtuozzo.com> (raw)

A CT with an AIO context fails to restore on a node with more possible
CPUs: io_setup() makes a bigger ring there, and CRIU needs the ring of
the dumped size. Skip the CPU heuristic of the ring size while the VE
is pseudosuper, and add a selftest for it.

https://virtuozzo.atlassian.net/browse/VSTOR-154129

---
Changes in v2:
- fs/aio: a ring restored below the minimum of this node doesn't use the
  per-CPU caches of free slots.
- fs/aio: say the VE is pseudosuper almost only for the restore.
- selftests/ve: destroy the VE when setup fails after make_ve(), and
  ASSERT_EQ for set_pseudosuper().
- Link to v1: http://lore.virtuozzo.com/20261113-pr-ptikhomirov-vstor-154129-aio-pseudosuper-ring-v1-0-7d35d143fdc3@virtuozzo.com

---
Pavel Tikhomirov (2):
      fs/aio: restore the AIO ring of the dumped size in a pseudosuper VE
      selftests/ve: check the AIO ring size in a pseudosuper VE

 fs/aio.c                                      |  21 ++-
 tools/testing/selftests/ve/.gitignore         |   1 +
 tools/testing/selftests/ve/Makefile           |   1 +
 tools/testing/selftests/ve/ve_aio_ring_test.c | 218 ++++++++++++++++++++++++++
 4 files changed, 240 insertions(+), 1 deletion(-)
---
base-commit: 3874c7f41089f93b796592c13b410ded6c987ec8
change-id: 20261113-pr-ptikhomirov-vstor-154129-aio-pseudosuper-ring-ae2133423a88

Best regards,
--  
Pavel Tikhomirov <ptikhomirov@virtuozzo.com>

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

             reply	other threads:[~2026-11-16 10:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 10:31 Pavel Tikhomirov [this message]
2026-11-16 10:31 ` [Devel] [PATCH hci-8.1 v2 1/2] fs/aio: restore the AIO ring of the dumped size in a pseudosuper VE Pavel Tikhomirov
2026-11-16 10:36   ` no-reply
2026-11-16 10:31 ` [Devel] [PATCH hci-8.1 v2 2/2] selftests/ve: check the AIO ring " Pavel Tikhomirov
2026-11-16 10:38   ` no-reply
2026-11-16 16:55 ` [Devel] [PATCH hci-8.1 v2 0/2] fs/aio: fix CT migration with AIO to a node with more CPUs Konstantin Khorenko
2026-11-16 16:55 ` 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=20261116-pr-ptikhomirov-vstor-154129-aio-pseudosuper-ring-v2-0-532d149b4bd7@virtuozzo.com \
    --to=ptikhomirov@virtuozzo.com \
    --cc=devel@openvz.org \
    --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.