From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Leonardo Bras <leobras@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Eric Blake <eblake@redhat.com>, Peter Xu <peterx@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v2 2/3] Add zero-copy-copied migration stat
Date: Mon, 4 Jul 2022 14:14:22 +0100 [thread overview]
Message-ID: <YsLnrgIGu5y88ZTu@redhat.com> (raw)
In-Reply-To: <87czelvxrt.fsf@pond.sub.org>
On Mon, Jul 04, 2022 at 02:59:50PM +0200, Markus Armbruster wrote:
> Daniel P. Berrangé <berrange@redhat.com> writes:
>
> > On Mon, Jul 04, 2022 at 02:04:41PM +0200, Markus Armbruster wrote:
>
> [...]
>
> >> Please rephrase the documentation of @zero-copy-copied in terms of
> >> @dirty-sync-count. Here's my attempt.
> >>
> >> # @zero-copy-copied: Number of times dirty RAM synchronization could not
> >> # avoid copying zero pages. This is between 0 and
> >> # @dirty-sync-count. (since 7.1)
> >
> > Any one have preferences on the name - i get slight put off by the
> > repeated word in the property name here.
> >
> > @zero-copy-rejects ?
> > @zero-copy-misses ?
> > @zero-copy-fails ?
>
> I'd consider any of these an improvement. Not a native speaker, but
> perhaps "failures" instead of "fails".
>
> We could also express the connection to @dirty-sync-count right in the
> name, like @dirty-sync-rejected-zero-copy, @dirty-sync-missed-zero-copy,
> @dirty-sync-failed-zero-copy. Or maybe -copies.
Yeah, @dirty-sync-missed-zero-copy is probably my favourite.
With 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 :|
next prev parent reply other threads:[~2022-07-04 13:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 15:59 [PATCH v2 0/3] Zero copy improvements (QIOChannel + multifd) Leonardo Bras
2022-07-01 15:59 ` [PATCH v2 1/3] QIOChannelSocket: Fix zero-copy flush returning code 1 when nothing sent Leonardo Bras
2022-07-01 15:59 ` [PATCH v2 2/3] Add zero-copy-copied migration stat Leonardo Bras
2022-07-04 6:18 ` Markus Armbruster
2022-07-04 9:06 ` Daniel P. Berrangé
2022-07-04 11:33 ` Markus Armbruster
2022-07-04 11:40 ` Dr. David Alan Gilbert
2022-07-04 12:04 ` Markus Armbruster
2022-07-04 12:16 ` Daniel P. Berrangé
2022-07-04 12:59 ` Markus Armbruster
2022-07-04 13:14 ` Daniel P. Berrangé [this message]
2022-07-04 18:13 ` Leonardo Brás
2022-07-05 4:14 ` Markus Armbruster
2022-07-01 15:59 ` [PATCH v2 3/3] migration/multifd: Warn user when zerocopy not working Leonardo Bras
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=YsLnrgIGu5y88ZTu@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 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.