From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: Manish Mishra <manish.mishra@nutanix.com>,
qemu-devel@nongnu.org, leobras@redhat.com, farosas@suse.de
Subject: Re: [PATCH v2] QIOChannelSocket: Flush zerocopy socket error queue on ENOBUF failure for sendmsg
Date: Tue, 11 Mar 2025 08:13:16 +0000 [thread overview]
Message-ID: <Z8_wnLIlfhM7bILZ@redhat.com> (raw)
In-Reply-To: <Z89FjreYuRjEeX1f@x1.local>
On Mon, Mar 10, 2025 at 04:03:26PM -0400, Peter Xu wrote:
> On Mon, Mar 10, 2025 at 07:48:16PM +0000, Daniel P. Berrangé wrote:
> > Given this is in public API, the data needs to remain reported accurately
> > for the whole deprecation period. IOW, the patch to qiochannel needs to
> > preserve this data too.
>
> :-(
>
> We could potentially mark MigrationStats to be experimental as a whole and
> declare that in deprecate.rst too, then after two releases, we can randomly
> add / remove fields as wish without always need to go through the
> deprecation process, am I right?
IMHO that would be an abuse of the process and harmful to applications
and users consuming stats.
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:[~2025-03-11 8:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 1:15 [PATCH v2] QIOChannelSocket: Flush zerocopy socket error queue on ENOBUF failure for sendmsg Manish Mishra
2025-03-10 19:12 ` Peter Xu
2025-03-10 19:48 ` Daniel P. Berrangé
2025-03-10 20:03 ` Peter Xu
2025-03-10 22:45 ` Manish
2025-03-11 15:22 ` Peter Xu
2025-03-11 15:30 ` Manish
2025-03-11 8:13 ` Daniel P. Berrangé [this message]
2025-03-11 15:20 ` Peter Xu
2025-03-11 15:33 ` Daniel P. Berrangé
2025-03-11 19:57 ` Peter Xu
2025-03-11 20:08 ` Daniel P. Berrangé
2025-03-11 21:37 ` 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=Z8_wnLIlfhM7bILZ@redhat.com \
--to=berrange@redhat.com \
--cc=farosas@suse.de \
--cc=leobras@redhat.com \
--cc=manish.mishra@nutanix.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.