From: "Denis V. Lunev" <den@openvz.org>
To: Pavel Butsykin <pbutsykin@virtuozzo.com>, qemu-devel@nongnu.org
Cc: quintela@redhat.com, amit.shah@redhat.com, eblake@redhat.com,
armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/2] migration capability to discard the migrated ram pages
Date: Wed, 25 Jan 2017 19:50:06 +0300 [thread overview]
Message-ID: <37c47ab8-362b-58ee-a49b-7ab32d20e037@openvz.org> (raw)
In-Reply-To: <20170116155113.21034-1-pbutsykin@virtuozzo.com>
On 01/16/2017 06:51 PM, Pavel Butsykin wrote:
> This feature frees the migrated memory on the source during postcopy-ram
> migration. In the second step of postcopy-ram migration when the source vm
> is put on pause we can free unnecessary memory. It will allow, in particular,
> to start relaxing the memory stress on the source host in a load-balancing
> scenario.
>
> Pavel Butsykin (2):
> add 'discard-ram' migrate capability
> migration: discard non-dirty ram pages after the start of postcopy
>
> include/migration/migration.h | 2 ++
> include/migration/qemu-file.h | 3 ++-
> migration/migration.c | 11 ++++++++
> migration/qemu-file.c | 59 ++++++++++++++++++++++++++++++++++++++-----
> migration/ram.c | 49 ++++++++++++++++++++++++++++++++++-
> qapi-schema.json | 5 +++-
> 6 files changed, 119 insertions(+), 10 deletions(-)
>
ping
prev parent reply other threads:[~2017-01-25 18:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 15:51 [Qemu-devel] [PATCH 0/2] migration capability to discard the migrated ram pages Pavel Butsykin
2017-01-16 15:51 ` [Qemu-devel] [PATCH 1/2] add 'discard-ram' migrate capability Pavel Butsykin
2017-01-27 11:01 ` Dr. David Alan Gilbert
2017-01-30 13:05 ` Pavel Butsykin
2017-01-16 15:51 ` [Qemu-devel] [PATCH 2/2] migration: discard non-dirty ram pages after the start of postcopy Pavel Butsykin
2017-01-27 11:39 ` Dr. David Alan Gilbert
2017-01-30 13:06 ` Pavel Butsykin
2017-01-17 3:33 ` [Qemu-devel] [PATCH 0/2] migration capability to discard the migrated ram pages no-reply
2017-01-25 16:50 ` Denis V. Lunev [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=37c47ab8-362b-58ee-a49b-7ab32d20e037@openvz.org \
--to=den@openvz.org \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=pbutsykin@virtuozzo.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).