OpenVZ / Virtuozzo kernel development (devel@openvz.org)
 help / color / mirror / Atom feed
From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>,
	Pavel Tikhomirov <ptikhomirov@virtuozzo.com>,
	cover.1789491989.git.vladimir.riabchun@virtuozzo.com,
	devel@openvz.org, Konstantin Khorenko <khorenko@virtuozzo.com>
Subject: Re: [Devel] [PATCH hci-8.1 v10 00/13] Add per-VE failcount support
Date: Fri, 25 Sep 2026 19:33:48 +0200	[thread overview]
Message-ID: <179035762821.3333433.11479053483037920081.b4-ty@b4> (raw)
In-Reply-To: <20260925-b4-kh-ve_fail-v10-0-77a6b6ea4205@virtuozzo.com>

On Fri, 25 Sep 2026 18:53:21 +0200, Konstantin Khorenko wrote:
> Add per-VE failcount support
> 
> This patchset introduces per-VE failcount support.
> We have several resources that have per-VE limits, the users might
> want to know what limit hits make operations fail.
> 
> - Patch 1 is cosmetic, nothing special.
> - Patches 2-4 change mount number and limit processing, unifying it
>   with other resources. VE selftest is updated in patch 3.
> - Patch 5 removes copy-pasted resource accessors by generating them
>   with macros.
> - Patch 6 is a split-out fix: ve0 was left without aio defaults when
>   aio_nr/aio_max_nr moved into ve_struct.
> - Patch 7 adds the ve.failcount file and the helpers.
> - Patches 8-12 add one failcounter each: netns, mnt, netif,
>   bpf_prog, aio.
> - Patch 13 introduces new VE selftest that checks mounts accounting,
>   limits and failcount updates.
> 
> [...]

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.4.vz10, thanks!

[01/13] ve/ve.{h, c}: farewell to spaces as indents
        https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/94e1f3e566b2
[02/13] ve/fs: count available mounts instead of used ones
        https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/b9c2e2d6ee85
[03/13] selftests/ve: update ve_ns_owner_test
        https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/81eba31300aa
[04/13] ve: make mount limit configurable per VE
        https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/dd2667127d88
[05/13] ve/ve.c: generate VE resource accessors using macros
        https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/d7411af14db5
[06/13] ve/aio: initialize aio fields in ve0
        https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/bc9ae303c2e3
[07/13] ve: introduce per-VE failcounter infrastructure
        https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/82fcf1c48466
[08/13] ve: add netns failcounter
        https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/edd7353a94df
[09/13] ve: add mnt failcounter
        https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/0f50eece91e9
[10/13] ve: add netif failcounter
        https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/4a6c30eb6f86
[11/13] ve: add bpf_prog failcounter
        https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/0755704f524a
[12/13] ve: add aio failcounter
        https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/77b09350431f
[13/13] selftests/ve: add mount accounting selftest
        https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/32609fbd61a6

-- 
Konstantin Khorenko <khorenko@virtuozzo.com>

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

      parent reply	other threads:[~2026-09-25 17:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 16:53 Konstantin Khorenko
2026-09-25 16:53 ` [Devel] [PATCH hci-8.1 v10 01/13] ve/ve.{h, c}: farewell to spaces as indents Konstantin Khorenko
2026-09-25 16:53 ` [Devel] [PATCH hci-8.1 v10 02/13] ve/fs: count available mounts instead of used ones Konstantin Khorenko
2026-09-25 16:53 ` [Devel] [PATCH hci-8.1 v10 03/13] selftests/ve: update ve_ns_owner_test Konstantin Khorenko
2026-09-25 16:53 ` [Devel] [PATCH hci-8.1 v10 04/13] ve: make mount limit configurable per VE Konstantin Khorenko
2026-09-25 16:53 ` [Devel] [PATCH hci-8.1 v10 05/13] ve/ve.c: generate VE resource accessors using macros Konstantin Khorenko
2026-09-25 16:53 ` [Devel] [PATCH hci-8.1 v10 06/13] ve/aio: initialize aio fields in ve0 Konstantin Khorenko
2026-09-25 16:53 ` [Devel] [PATCH hci-8.1 v10 07/13] ve: introduce per-VE failcounter infrastructure Konstantin Khorenko
2026-09-25 16:53 ` [Devel] [PATCH hci-8.1 v10 08/13] ve: add netns failcounter Konstantin Khorenko
2026-09-25 16:53 ` [Devel] [PATCH hci-8.1 v10 09/13] ve: add mnt failcounter Konstantin Khorenko
2026-09-25 16:53 ` [Devel] [PATCH hci-8.1 v10 10/13] ve: add netif failcounter Konstantin Khorenko
2026-09-25 16:53 ` [Devel] [PATCH hci-8.1 v10 11/13] ve: add bpf_prog failcounter Konstantin Khorenko
2026-09-25 16:53 ` [Devel] [PATCH hci-8.1 v10 12/13] ve: add aio failcounter Konstantin Khorenko
2026-09-25 16:53 ` [Devel] [PATCH hci-8.1 v10 13/13] selftests/ve: add mount accounting selftest Konstantin Khorenko
2026-09-25 17:10 ` [Devel] [PATCH hci-8.1 v10 00/13] Add per-VE failcount support Vladimir Riabchun
2026-09-25 17:33 ` 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=179035762821.3333433.11479053483037920081.b4-ty@b4 \
    --to=khorenko@virtuozzo.com \
    --cc=cover.1789491989.git.vladimir.riabchun@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