From: Andrey Gruzdev <andrey.gruzdev@virtuozzo.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, Den Lunev <den@openvz.org>,
Eric Blake <eblake@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Juan Quintela <quintela@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH v4 6/6] introduce simple linear scan rate limiting mechanism
Date: Mon, 30 Nov 2020 11:11:00 +0300 [thread overview]
Message-ID: <ab27e287-b737-25a7-cfed-2d70e0042537@virtuozzo.com> (raw)
In-Reply-To: <20201127222811.GJ6573@xz-x1>
On 28.11.2020 01:28, Peter Xu wrote:
> On Thu, Nov 26, 2020 at 06:17:34PM +0300, Andrey Gruzdev wrote:
>> Since reading UFFD events and saving paged data are performed
>> from the same thread, write fault latencies are sensitive to
>> migration stream stalls. Limiting total page saving rate is a
>> method to reduce amount of noticiable fault resolution latencies.
>>
>> Migration bandwidth limiting is achieved via noticing cases of
>> out-of-threshold write fault latencies and temporarily disabling
>> (strictly speaking, severely throttling) saving non-faulting pages.
>
> So have you done any measurements out of it, as we've talked in previous
> version? Thanks,
>
Sorry, not done yet.
--
Andrey Gruzdev, Principal Engineer
Virtuozzo GmbH +7-903-247-6397
virtuzzo.com
next prev parent reply other threads:[~2020-11-30 8:12 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 15:17 [PATCH v4 0/6] UFFD write-tracking migration/snapshots Andrey Gruzdev via
2020-11-26 15:17 ` [PATCH v4 1/6] introduce 'background-snapshot' migration capability Andrey Gruzdev via
2020-11-27 19:55 ` Peter Xu
2020-11-28 16:35 ` Andrey Gruzdev
2020-11-26 15:17 ` [PATCH v4 2/6] introduce UFFD-WP low-level interface helpers Andrey Gruzdev via
2020-11-27 21:04 ` Peter Xu
2020-11-29 20:12 ` Andrey Gruzdev
2020-11-30 15:34 ` Peter Xu
2020-11-30 18:41 ` Andrey Gruzdev
2020-12-01 12:24 ` Dr. David Alan Gilbert
2020-12-01 19:32 ` Andrey Gruzdev
2020-11-26 15:17 ` [PATCH v4 3/6] support UFFD write fault processing in ram_save_iterate() Andrey Gruzdev via
2020-11-27 21:49 ` Peter Xu
2020-11-29 21:14 ` Andrey Gruzdev
2020-11-30 16:32 ` Peter Xu
2020-11-30 19:27 ` Andrey Gruzdev
2020-11-26 15:17 ` [PATCH v4 4/6] implementation of background snapshot thread Andrey Gruzdev via
2020-11-26 15:17 ` [PATCH v4 5/6] the rest of write tracking migration code Andrey Gruzdev via
2020-11-27 22:26 ` Peter Xu
2020-11-30 8:09 ` Andrey Gruzdev
2020-11-26 15:17 ` [PATCH v4 6/6] introduce simple linear scan rate limiting mechanism Andrey Gruzdev via
2020-11-27 22:28 ` Peter Xu
2020-11-30 8:11 ` Andrey Gruzdev [this message]
2020-11-30 16:40 ` Peter Xu
2020-11-30 19:30 ` Andrey Gruzdev
2020-11-26 15:47 ` [PATCH v4 0/6] UFFD write-tracking migration/snapshots Peter Krempa
2020-11-27 8:21 ` Andrey Gruzdev
2020-11-27 9:49 ` Peter Krempa
2020-11-27 10:00 ` Andrey Gruzdev
2020-11-27 15:45 ` Peter Xu
2020-11-27 17:19 ` Andrey Gruzdev
2020-11-27 22:04 ` Peter Xu
2020-11-30 8:07 ` Andrey Gruzdev
2020-12-01 7:08 ` Peter Krempa
2020-12-01 8:42 ` Andrey Gruzdev
2020-12-01 10:53 ` Peter Krempa
2020-12-01 11:24 ` Andrey Gruzdev
2020-12-01 18:40 ` Dr. David Alan Gilbert
2020-12-01 19:22 ` Peter Xu
2020-12-01 20:01 ` Dr. David Alan Gilbert
2020-12-01 20:29 ` Andrey Gruzdev
2020-12-01 20:11 ` Andrey Gruzdev
2020-12-01 18:54 ` Peter Xu
2020-12-01 20:00 ` Dr. David Alan Gilbert
2020-12-01 20:26 ` Andrey Gruzdev
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=ab27e287-b737-25a7-cfed-2d70e0042537@virtuozzo.com \
--to=andrey.gruzdev@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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;
as well as URLs for NNTP newsgroup(s).