From: Leonardo Bras Soares Passos <leobras@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Peter Xu" <peterx@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Eric Blake" <eblake@redhat.com>
Subject: Re: [PATCH v7 3/5] migration: Add zero-copy parameter for QMP/HMP for Linux
Date: Mon, 21 Feb 2022 13:23:35 -0300 [thread overview]
Message-ID: <CAJ6HWG6d0jNdnncXjLqPWC_sSfGa69jFJVnecpMoPO51-r8Mzg@mail.gmail.com> (raw)
In-Reply-To: <87zgmocf0t.fsf@secure.mitica>
Hello Juan,
Thanks for thew feedback!
On Fri, Feb 18, 2022 at 1:31 PM Juan Quintela <quintela@redhat.com> wrote:
>
> Leonardo Bras Soares Passos <leobras@redhat.com> wrote:
> > On Wed, Jan 19, 2022 at 3:16 PM Daniel P. Berrangé <berrange@redhat.com> wrote:
> >>
> >> On Wed, Jan 19, 2022 at 03:03:29PM -0300, Leonardo Bras Soares Passos wrote:
> >> > Hello Daniel,
> >> >
> >> > On Thu, Jan 13, 2022 at 10:10 AM Daniel P. Berrangé <berrange@redhat.com> wrote:
> >> > >
> >> > > On Thu, Jan 06, 2022 at 07:13:40PM -0300, Leonardo Bras wrote:
> >> > > > Add property that allows zero-copy migration of memory pages,
> >> > > > and also includes a helper function migrate_use_zero_copy() to check
> >> > > > if it's enabled.
> >> > > >
> >> > > > No code is introduced to actually do the migration, but it allow
> >> > > > future implementations to enable/disable this feature.
> >> > > >
> >> > > > On non-Linux builds this parameter is compiled-out.
> >> > > >
> >> > > > Signed-off-by: Leonardo Bras <leobras@redhat.com>
> >> > > > ---
> >> > > > qapi/migration.json | 24 ++++++++++++++++++++++++
> >> > > > migration/migration.h | 5 +++++
> >> > > > migration/migration.c | 32 ++++++++++++++++++++++++++++++++
> >> > > > migration/socket.c | 5 +++++
> >> > > > monitor/hmp-cmds.c | 6 ++++++
> >> > > > 5 files changed, 72 insertions(+)
> >> > >
> >> > > Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> >> >
> >> > Thanks!
> >>
> >
> > Ok, I see the point.
> > I will try to refactor the code changing zero-copy to zero-copy-send
> > or something like that.
>
> Hi
>
> I am late to the party, but I agree with Dan that we need two flags.
>
> Thre reason is that you can be the target of one migration, and later be
> the source of a next one. If we only have one flag that means different
> things on the source and destination side, things become really
> complicated.
>
> Later, Juan.
>
Yeah, that makes sense. :)
Best regards,
Leo
next prev parent reply other threads:[~2022-02-21 16:33 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 22:13 [PATCH v7 0/5] MSG_ZEROCOPY + multifd Leonardo Bras
2022-01-06 22:13 ` [PATCH v7 1/5] QIOChannel: Add flags on io_writev and introduce io_flush callback Leonardo Bras
2022-01-13 6:28 ` Peter Xu
2022-01-18 20:45 ` Leonardo Bras Soares Passos
2022-01-19 1:58 ` Peter Xu
2022-01-19 18:29 ` Leonardo Bras Soares Passos
2022-01-13 10:52 ` Daniel P. Berrangé
2022-01-19 4:38 ` Leonardo Bras Soares Passos
2022-01-06 22:13 ` [PATCH v7 2/5] QIOChannelSocket: Implement io_writev zero copy flag & io_flush for CONFIG_LINUX Leonardo Bras
2022-01-13 6:48 ` Peter Xu
2022-01-13 10:06 ` Daniel P. Berrangé
2022-01-13 10:34 ` Peter Xu
2022-01-13 10:42 ` Daniel P. Berrangé
2022-01-13 12:12 ` Peter Xu
2022-01-19 17:23 ` Leonardo Bras Soares Passos
2022-01-19 17:22 ` Leonardo Bras Soares Passos
2022-01-20 1:28 ` Peter Xu
2022-01-19 17:16 ` Leonardo Bras Soares Passos
2022-01-19 17:01 ` Leonardo Bras Soares Passos
2022-02-01 4:23 ` Leonardo Bras Soares Passos
2022-01-13 13:05 ` Daniel P. Berrangé
2022-01-19 17:24 ` Leonardo Bras Soares Passos
2022-01-06 22:13 ` [PATCH v7 3/5] migration: Add zero-copy parameter for QMP/HMP for Linux Leonardo Bras
2022-01-13 7:00 ` Peter Xu
2022-01-19 17:53 ` Leonardo Bras Soares Passos
2022-01-13 13:09 ` Daniel P. Berrangé
2022-01-19 18:03 ` Leonardo Bras Soares Passos
2022-01-19 18:15 ` Daniel P. Berrangé
2022-01-19 18:46 ` Leonardo Bras Soares Passos
2022-02-18 16:31 ` Juan Quintela
2022-02-21 16:23 ` Leonardo Bras Soares Passos [this message]
2022-01-06 22:13 ` [PATCH v7 4/5] migration: Add migrate_use_tls() helper Leonardo Bras
2022-01-13 7:02 ` Peter Xu
2022-01-19 18:06 ` Leonardo Bras Soares Passos
2022-01-20 1:37 ` Peter Xu
2022-01-13 13:10 ` Daniel P. Berrangé
2022-01-19 18:07 ` Leonardo Bras Soares Passos
2022-01-06 22:13 ` [PATCH v7 5/5] multifd: Implement zero copy write in multifd migration (multifd-zero-copy) Leonardo Bras
2022-01-13 7:15 ` Peter Xu
2022-01-19 18:23 ` Leonardo Bras Soares Passos
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=CAJ6HWG6d0jNdnncXjLqPWC_sSfGa69jFJVnecpMoPO51-r8Mzg@mail.gmail.com \
--to=leobras@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@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).