[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RESEND PATCH 2/2] migration: report multiFd related thread pid to l
|
From: |
Daniel P . Berrangé |
|
Subject: |
Re: [RESEND PATCH 2/2] migration: report multiFd related thread pid to libvirt |
|
Date: |
Wed, 11 Jan 2023 19:04:11 +0000 |
|
User-agent: |
Mutt/2.2.9 (2022-11-12) |
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 :|