From: Juan Quintela <quintela@redhat.com>
To: Jiang Jiacheng <jiangjiacheng@huawei.com>
Cc: <qemu-devel@nongnu.org>, <berrange@redhat.com>,
<dgilbert@redhat.com>, <yubihong@huawei.com>,
<xiexiangyou@huawei.com>, <zhengchuan@huawei.com>,
<linyilu@huawei.com>
Subject: Re: [PATCH 3/3] migration: save/delete migration thread info
Date: Mon, 30 Jan 2023 15:04:42 +0100 [thread overview]
Message-ID: <87357sp18l.fsf@secure.mitica> (raw)
In-Reply-To: <b059cf27-73dd-addf-58bb-2078c3aa985f@huawei.com> (Jiang Jiacheng's message of "Mon, 30 Jan 2023 20:49:11 +0800")
Jiang Jiacheng <jiangjiacheng@huawei.com> wrote:
> On 2023/1/30 12:28, Juan Quintela wrote:
>> Jiang Jiacheng <jiangjiacheng@huawei.com> wrote:
>>> To support query migration thread infomation, save and delete
>>> thread information at thread creation and end.
>>>
>>> Signed-off-by: Jiang Jiacheng <jiangjiacheng@huawei.com>
>>
>> Don't disagree with this, but if we create this on the sending side, why
>> this is not needed for the multifd_recv_threads?
>>
>
> I only add several threads which i'm interested in into the list till
> now, whose information will be used for setting cpu affinity for
> migration thread.
> For consistency, we can add other threads to the list, but those
> information won't be used so far.
It is just curiosity, why do you want to set cpu affinity on the source
but not on destination?
Later, Juan.
next prev parent reply other threads:[~2023-01-30 14:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 8:47 [RFC PATCH 0/3] migration: support query migration thread information Jiang Jiacheng via
2023-01-20 8:47 ` [PATCH 1/3] migration: report migration thread name to libvirt Jiang Jiacheng via
2023-01-30 4:19 ` Juan Quintela
2023-01-30 12:48 ` Jiang Jiacheng via
2023-01-20 8:47 ` [PATCH 2/3] migration: implement query migration threadinfo by name Jiang Jiacheng via
2023-01-30 4:27 ` Juan Quintela
2023-01-30 12:48 ` Jiang Jiacheng via
2023-01-30 14:03 ` Juan Quintela
2023-01-31 13:00 ` Jiang Jiacheng via
2023-01-31 16:33 ` Juan Quintela
2023-01-20 8:47 ` [PATCH 3/3] migration: save/delete migration thread info Jiang Jiacheng via
2023-01-30 4:28 ` Juan Quintela
2023-01-30 12:49 ` Jiang Jiacheng via
2023-01-30 14:04 ` Juan Quintela [this message]
2023-01-31 13:00 ` 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=87357sp18l.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jiangjiacheng@huawei.com \
--cc=linyilu@huawei.com \
--cc=qemu-devel@nongnu.org \
--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.