From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Jiang Jiacheng <jiangjiacheng@huawei.com>,
jdenemar@redhat.com, qemu-devel@nongnu.org, quintela@redhat.com,
yubihong@huawei.com, xiexiangyou@huawei.com,
zhengchuan@huawei.com, linyilu@huawei.com
Subject: Re: [RESEND PATCH 2/2] migration: report multiFd related thread pid to libvirt
Date: Wed, 11 Jan 2023 19:04:11 +0000 [thread overview]
Message-ID: <Y78IK7KuJ4zalm2p@redhat.com> (raw)
In-Reply-To: <Y78HZb0AG55Yp/i/@work-vm>
On Wed, Jan 11, 2023 at 07:00:53PM +0000, Dr. David Alan Gilbert wrote:
> * Jiang Jiacheng via (qemu-devel@nongnu.org) wrote:
> > From: Zheng Chuan <zhengchuan@huawei.com>
> >
> > Report multiFd related thread pid to libvirt in order to
> > pin multiFd thread to different cpu.
>
> With multifd you may well want to pin different multifd threads
> to different cores; so you need to include the 'id' and 'name' fields of
> the multifd thread in the event.
Are the 'id' / 'name' fields considered stable API for QEMU ?
IIRC, the mgmt app merely requests the number of multifd threads
and doesn't assign any identifying names/ids to them, unlike
iothreads where the mgmt app gives an explicit 'id'.
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:[~2023-01-11 19:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 12:12 [RESEND PATCH 0/2] migration: Report migration related thread pid to libvirt to support migration pin Jiang Jiacheng via
2023-01-09 12:12 ` [RESEND PATCH 1/2] migration: report migration related thread pid to libvirt Jiang Jiacheng via
2023-01-09 12:12 ` [RESEND PATCH 2/2] migration: report multiFd " Jiang Jiacheng via
2023-01-11 19:00 ` Dr. David Alan Gilbert
2023-01-11 19:04 ` Daniel P. Berrangé [this message]
2023-01-12 9:24 ` Jiang Jiacheng via
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=Y78IK7KuJ4zalm2p@redhat.com \
--to=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jdenemar@redhat.com \
--cc=jiangjiacheng@huawei.com \
--cc=linyilu@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=xiexiangyou@huawei.com \
--cc=yubihong@huawei.com \
--cc=zhengchuan@huawei.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.