|
From: | Jason Wang |
Subject: | Re: [Qemu-devel] [PATCH 02/15] colo-compare: implement the process of checkpoint |
Date: | Fri, 14 Apr 2017 14:38:40 +0800 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
On 2017年04月14日 14:22, Hailiang Zhang wrote:
Hi Jason, On 2017/4/14 13:57, Jason Wang wrote:On 2017年02月22日 17:31, Zhang Chen wrote:On 02/22/2017 11:42 AM, zhanghailiang wrote:While do checkpoint, we need to flush all the unhandled packets, By using the filter notifier mechanism, we can easily to notify every compare object to do this process, which runs inside of compare threads as a coroutine.Hi~ Jason and Hailiang. I will send a patch set later about colo-compare notify mechanism for Xen like this patch. I want to add a new chardev socket way in colo-comapre connect to Xen colo, for notify checkpoint or failover, Because We have no choice to use this way communicate with Xen codes. That's means we will have two notify mechanism. What do you think about this? Thanks Zhang ChenI was thinking the possibility of using similar way to for colo compare. E.g can we use socket? This can saves duplicated codes more or less.Since there are too many sockets used by filter and COLO, (Two unix sockets and two tcp sockets for each vNIC), I don't want to introduce more ;) , but i'm not sure if it is possible to make it more flexible and optional, abstract these duplicated codes, pass the opened fd (No matter eventfd or socket fd ) as parameter, for example.Is this way acceptable ? Thanks, Hailiang
Yes, that's kind of what I want. We don't want to use two message format. Passing a opened fd need management support, we still need a fallback if there's no management on top. For qemu/kvm, we can do all stuffs transparent to the cli by e.g socketpair() or others, but the key is to have a unified message format.
Thoughts? Thanks
Thanks .
[Prev in Thread] | Current Thread | [Next in Thread] |