From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 v3 0/1] selftests: bpf: fix test_lru_sanity3
Date: Fri, 25 Sep 2026 19:26:10 +0200 [thread overview]
Message-ID: <179035717009.3329592.1430155725212948556.b4-ty@b4> (raw)
In-Reply-To: <20260925152929.3669459-1-eva.kurchatova@virtuozzo.com>
On Fri, 25 Sep 2026 18:27:54 +0300, Eva Kurchatova wrote:
> selftests: bpf: fix test_lru_sanity3
>
> Patchset for tast https://virtuozzo.atlassian.net/browse/VSTOR-139677
>
> Changes in v3:
> - Skip the test where __tgt_size(tgt_free) is 0 instead of forcing
> batch_size to 1. With one element per refill the forced shrink on the
> last insert evicts a live key, so v2 failed above 128 cpus, where the
> original test still passed by degenerating.
> - Drop assert(__tgt_size(map_size) == batch_size), it holds for every
> batch_size and cpu count and checked nothing.
> - Cut the comment above map_size to one line.
> - Reword to better understand the cause of the failure.
> - Sent alone, the rest of the v2 series is merged.
>
> [...]
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!
[1/1] selftests: bpf: size the map in test_lru_sanity3 to whole refills
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/34899b07b40f
--
Konstantin Khorenko <khorenko@virtuozzo.com>
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
prev parent reply other threads:[~2026-09-25 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 15:27 Eva Kurchatova
2026-09-25 15:27 ` [Devel] [PATCH hci-8.1 v3 1/1] selftests: bpf: size the map in test_lru_sanity3 to whole refills Eva Kurchatova
2026-09-25 17:16 ` Konstantin Khorenko
2026-09-25 17:26 ` 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=179035717009.3329592.1430155725212948556.b4-ty@b4 \
--to=khorenko@virtuozzo.com \
--cc=devel@openvz.org \
--cc=eva.kurchatova@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.