From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH vz10 v2 1/2] ms/selftests/damon/damon_nr_regions: set ops update for merge results check to 100ms
Date: Wed, 02 Sep 2026 19:56:42 +0200 [thread overview]
Message-ID: <178837180259.1246724.2520519948216002382.b4-review@b4> (raw)
In-Reply-To: <20260831231328.1644755-1-eva.kurchatova@virtuozzo.com>
On Tue, 01 Sep 2026 02:13:25 +0300, Eva Kurchatova <eva.kurchatova@virtuozzo.com> wrote:
> damon_nr_regions.py updates max_nr_regions to a number smaller than
> expected number of real regions and confirms DAMON respect the harsh
> limit. To give time for DAMON to make changes for the regions, 3
> aggregation intervals (300 milliseconds) are given.
>
> The internal mechanism works with not only the max_nr_regions, but also
> sz_limit, though. It avoids merging region if that casn make region of
> size larger than sz_limit. In the test, sz_limit is set too small to
> achive the new max_nr_regions, unless it is updated for the new
> min_nr_regions. But the update is done only once per operations set
> update interval, which is one second by default.
>
> [...]
Reviewed-by: Konstantin Khorenko <khorenko@virtuozzo.com>
--
Konstantin Khorenko <khorenko@virtuozzo.com>
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next prev parent reply other threads:[~2026-09-02 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 23:13 Eva Kurchatova
2026-08-31 23:13 ` [Devel] [PATCH vz10 v2 2/2] ms/selftests/damon/damon_nr_regions: sort collected regiosn before checking with min/max boundaries Eva Kurchatova
2026-09-02 17:56 ` Konstantin Khorenko
2026-09-02 17:56 ` Konstantin Khorenko [this message]
2026-09-02 17:59 ` [Devel] [PATCH vz10 v2 1/2] ms/selftests/damon/damon_nr_regions: set ops update for merge results check to 100ms 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=178837180259.1246724.2520519948216002382.b4-review@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox