Re: [RESEND PATCH 2/2] migration: report multiFd related thread pid to libvirt

2023-01-12 Thread Jiang Jiacheng via
On 2023/1/12 3:04, Daniel P. Berrangé wrote: > On Wed, Jan 11, 2023 at 07:00:53PM +, Dr. David Alan Gilbert wrote: >> * Jiang Jiacheng via (qemu-devel@nongnu.org) wrote: >>> From: Zheng Chuan >>> >>> Report multiFd related thread pid to libvirt in order to >>> pin multiFd thread to differen

Re: [RESEND PATCH 2/2] migration: report multiFd related thread pid to libvirt

2023-01-11 Thread Daniel P . Berrangé
On Wed, Jan 11, 2023 at 07:00:53PM +, Dr. David Alan Gilbert wrote: > * Jiang Jiacheng via (qemu-devel@nongnu.org) wrote: > > From: Zheng Chuan > > > > Report multiFd related thread pid to libvirt in order to > > pin multiFd thread to different cpu. > > With multifd you may well want to pin

Re: [RESEND PATCH 2/2] migration: report multiFd related thread pid to libvirt

2023-01-11 Thread Dr. David Alan Gilbert
* Jiang Jiacheng via (qemu-devel@nongnu.org) wrote: > From: Zheng Chuan > > 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 'nam

[RESEND PATCH 2/2] migration: report multiFd related thread pid to libvirt

2023-01-09 Thread Jiang Jiacheng via
From: Zheng Chuan Report multiFd related thread pid to libvirt in order to pin multiFd thread to different cpu. --- migration/multifd.c | 4 qapi/migration.json | 12 2 files changed, 16 insertions(+) diff --git a/migration/multifd.c b/migration/multifd.c index 000ca4d4ec..f3