qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Leonardo Bras Soares Passos <leobras@redhat.com>
Cc: Juan Quintela <quintela@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>, Peter Xu <peterx@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	Eric Blake <eblake@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH v7 3/5] migration: Add zero-copy parameter for QMP/HMP for Linux
Date: Wed, 19 Jan 2022 18:15:12 +0000	[thread overview]
Message-ID: <YehVMEL1hPaTbCIE@redhat.com> (raw)
In-Reply-To: <CAJ6HWG4GQV1N_=18TPqQygKCz36+VBx=b4EtUoZpMvcOQ6v0Vg@mail.gmail.com>

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!
> 
> >
> > >
> > > diff --git a/qapi/migration.json b/qapi/migration.json
> > > index bbfd48cf0b..2e62ea6ebd 100644
> > > --- a/qapi/migration.json
> > > +++ b/qapi/migration.json
> > > @@ -730,6 +730,13 @@
> > >  #                      will consume more CPU.
> > >  #                      Defaults to 1. (Since 5.0)
> > >  #
> > > +# @zero-copy: Controls behavior on sending memory pages on migration.
> > > +#             When true, enables a zero-copy mechanism for sending memory
> > > +#             pages, if host supports it.
> > > +#             Requires that QEMU be permitted to use locked memory for guest
> > > +#             RAM pages.
> > > +#             Defaults to false. (Since 7.0)
> > > +#
> > >  # @block-bitmap-mapping: Maps block nodes and bitmaps on them to
> > >  #                        aliases for the purpose of dirty bitmap migration.  Such
> > >  #                        aliases may for example be the corresponding names on the
> > > @@ -769,6 +776,7 @@
> > >             'xbzrle-cache-size', 'max-postcopy-bandwidth',
> > >             'max-cpu-throttle', 'multifd-compression',
> > >             'multifd-zlib-level' ,'multifd-zstd-level',
> > > +           { 'name': 'zero-copy', 'if' : 'CONFIG_LINUX'},
> > >             'block-bitmap-mapping' ] }
> > >
> > >  ##
> > > @@ -895,6 +903,13 @@
> > >  #                      will consume more CPU.
> > >  #                      Defaults to 1. (Since 5.0)
> > >  #
> > > +# @zero-copy: Controls behavior on sending memory pages on migration.
> > > +#             When true, enables a zero-copy mechanism for sending memory
> > > +#             pages, if host supports it.
> > > +#             Requires that QEMU be permitted to use locked memory for guest
> > > +#             RAM pages.
> > > +#             Defaults to false. (Since 7.0)
> > > +#
> > >  # @block-bitmap-mapping: Maps block nodes and bitmaps on them to
> > >  #                        aliases for the purpose of dirty bitmap migration.  Such
> > >  #                        aliases may for example be the corresponding names on the
> > > @@ -949,6 +964,7 @@
> > >              '*multifd-compression': 'MultiFDCompression',
> > >              '*multifd-zlib-level': 'uint8',
> > >              '*multifd-zstd-level': 'uint8',
> > > +            '*zero-copy': { 'type': 'bool', 'if': 'CONFIG_LINUX' },
> > >              '*block-bitmap-mapping': [ 'BitmapMigrationNodeAlias' ] } }
> >
> > The current zerocopy impl is for the send path.
> >
> > Do you expect we might get zerocopy in the receive path
> > later ?
> 
> It's possible, but I haven't started the implementation yet.
> 
> >
> > If so then either call this 'send-zero-copy', or change it
> > from a bool to an enum taking '["send", "recv", "both"]'.
> >
> > I'd probably take the former and just rename it.
> >
> 
> Well, my rationale:
> - I want to set zero copy sending:
> zero-copy is set in the sending host, start migration.
> 
> - I want to set zero copy receiving:
> zero-copy is set in the receiving host, wait for migration.
> (Of course host support is checked when setting the parameter).
> 
> The problem with the current approach is trying to enable zero-copy on
> receive before it's implemented, which will 'fail' silently .
> A possible solution would be to add a patch to check in the receiving
> path if zero-copy is enabled, and fail for now.

That's not good because mgmt apps cannot query the QAPI schema
to find out if this feature is supported or not.

If we wantt o support zero copy recv, then we need an explicit
flag for it that is distinct from zero copy send, so that apps
can introspect whether the feature is implemneted in QEMU or
not.

Distinct named bool flags feels better, and also makes it clear
to anyone not familiar with the impl that the current  code is
strictly send only.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2022-01-19 18:17 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é [this message]
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
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=YehVMEL1hPaTbCIE@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@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 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).