All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artyom <starardev@gmail.com>
To: Peter Xu <peterx@redhat.com>
Cc: leobras@redhat.com, qemu-devel@nongnu.org, dgilbert@redhat.com,
	quintela@redhat.com
Subject: Re: Live Migration ToDo
Date: Tue, 26 Apr 2022 01:39:58 +0300	[thread overview]
Message-ID: <CA+inuZ_o5eyc+dFyTxKe1v1nw8fmhXP1P4gysY0+L7N6VRtMwQ@mail.gmail.com> (raw)
In-Reply-To: <YmbpoyhTXB4jdgx+@xz-m1.local>

[-- Attachment #1: Type: text/plain, Size: 1623 bytes --]

Thank you for your response. Yes, I would like to work on some task, and
eventually I would like to use it as my student project. For example, it
might be possible to implement the technique from the article Post-Copy,
Hines, 2009: demand paging, active push, prepaging and dynamic
self-ballooning. As far as I understood from the postcopy documentation,
the pages are pushed sequentially, but it is possible to implement a new
prepaging strategy. Or are there any obstacles to implementing the ideas of
this paper in QEMU?

On Mon, Apr 25, 2022 at 9:34 PM Peter Xu <peterx@redhat.com> wrote:

> Hi,
>
> On Mon, Apr 25, 2022 at 01:41:27PM +0300, Artyom wrote:
> > Hello! I would like to see a list of suggestions/ideas/tickets for
> > improving live migration (especially performance and algorithms). There
> is
> > a page https://wiki.qemu.org/ToDo/LiveMigration, but it has not been
> > updated for a long time. Thanks
>
> Yes I think you're right and it's a good idea we should at some point
> revive the page so it always contains up-to-date contents.
>
> Do you mean that you want to contribute to QEMU project by working on some
> (obviously, not bit-sized) performance related tasks on live migration to
> improve the software?
>
> So far I am aware that Leonardo was working on zero-copy sender side for
> it, Juan was experimenting some bitmap split researches, and I'm working on
> a bit of the postcopy specific enhancements.  I'm not sure what I can do
> here to help you start any form of contribution, maybe starting from
> knowing more context of what you want and plan. :)
>
> Thanks,
>
> --
> Peter Xu
>
>

[-- Attachment #2: Type: text/html, Size: 2124 bytes --]

  reply	other threads:[~2022-04-25 22:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25 10:41 Live Migration ToDo Artyom
2022-04-25 18:34 ` Peter Xu
2022-04-25 22:39   ` Artyom [this message]
2022-04-25 22:51     ` Peter Xu
2022-04-25 23:17       ` Artyom
2022-04-25 23:33         ` Peter Xu

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=CA+inuZ_o5eyc+dFyTxKe1v1nw8fmhXP1P4gysY0+L7N6VRtMwQ@mail.gmail.com \
    --to=starardev@gmail.com \
    --cc=dgilbert@redhat.com \
    --cc=leobras@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 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.