From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Alexey Kuznetsov <kuznet@virtuozzo.com>,
devel@openvz.org, Konstantin Khorenko <khorenko@virtuozzo.com>
Subject: Re: [Devel] [PATCH hci-8.1 0/2] ext4: replace the vz prefetch test_bit patch with the mainstream one
Date: Tue, 22 Sep 2026 15:31:24 +0200 [thread overview]
Message-ID: <179008388473.3011502.4154628376086916620.b4-ty@b4> (raw)
In-Reply-To: <20260922-pr-khorenko-vstor-145663-ext4-ms-v1-0-4dd83d495810@virtuozzo.com>
On Tue, 22 Sep 2026 15:27:46 +0200, Konstantin Khorenko wrote:
> ext4: replace the vz prefetch test_bit patch with the mainstream one
>
> The vz patch 3fff8724d1f89 ("fs/ext4: do not run test_and_set_bit on
> every prefetch scan") went in for VSTOR-137147 to stop
> ext4_mb_prefetch() from doing a locked test_and_set_bit on bb_state of
> every group it walks. The bit is set-only, yet the atomic RMW took the
> ext4_group_info cache line exclusive on every pass and bounced it
> between allocating threads.
>
> [...]
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.2.vz10, thanks!
[1/2] Revert "fs/ext4: do not run test_and_set_bit on every prefetch scan"
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/52ea9a9ab754
[2/2] ext4: avoid RWM atomic in EXT4_MB_GRP_TEST_AND_SET_READ
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/7ecb7901c306
--
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-22 13:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 13:27 Konstantin Khorenko
2026-09-22 13:27 ` [Devel] [PATCH hci-8.1 1/2] Revert "fs/ext4: do not run test_and_set_bit on every prefetch scan" Konstantin Khorenko
2026-09-22 13:27 ` [Devel] [PATCH hci-8.1 2/2] ext4: avoid RWM atomic in EXT4_MB_GRP_TEST_AND_SET_READ Konstantin Khorenko
2026-09-22 13:31 ` 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=179008388473.3011502.4154628376086916620.b4-ty@b4 \
--to=khorenko@virtuozzo.com \
--cc=devel@openvz.org \
--cc=kuznet@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