* Zhang Chen (zhangchen.f...@cn.fujitsu.com) wrote:
>
>
> On 11/10/2015 06:54 PM, Dr. David Alan Gilbert wrote:
> >* Tkid (zhangchen.f...@cn.fujitsu.com) wrote:
> >>(3)SN Qemu COLO-Proxy recieve SVM's packets and forward to PN Qemu
> >>COLO-Proxy.
> >What protocol are you using for the data car
* Jason Wang (jasow...@redhat.com) wrote:
>
>
> On 11/10/2015 05:41 PM, Dr. David Alan Gilbert wrote:
> > * Jason Wang (jasow...@redhat.com) wrote:
> >>
> >> On 11/10/2015 01:26 PM, Tkid wrote:
> >>> Hi,all
> >>>
> >>> We are planning to reimplement colo proxy in userspace (Here is in
> >>> qemu)
On 11/11/2015 09:23 AM, Dong, Eddie wrote:
>> - What's the plan for vhost? Userspace network in qemu is rather slow, most
>> user will choose vhost.
> [Dong, Eddie] Hi Jason:
> How about we take staging approach? In general, COLO opens a door of
> high performance HA solution, but it will
On 11/10/2015 05:41 PM, Dr. David Alan Gilbert wrote:
> * Jason Wang (jasow...@redhat.com) wrote:
>>
>> On 11/10/2015 01:26 PM, Tkid wrote:
>>> Hi,all
>>>
>>> We are planning to reimplement colo proxy in userspace (Here is in
>>> qemu) to
>>> cache and compare net packets.This module is one of th
On 11/10/2015 05:35 PM, Tkid wrote:
>
>
> On 11/10/2015 03:35 PM, Jason Wang wrote:
>> On 11/10/2015 01:26 PM, Tkid wrote:
>>> Hi,all
>>>
>>> We are planning to reimplement colo proxy in userspace (Here is in
>>> qemu) to
>>> cache and compare net packets.This module is one of the important
>>> c
On 11/10/2015 06:54 PM, Dr. David Alan Gilbert wrote:
* Tkid (zhangchen.f...@cn.fujitsu.com) wrote:
Hi,all
We are planning to reimplement colo proxy in userspace (Here is in qemu) to
cache and compare net packets.This module is one of the important components
of COLO project and now it is sti
On 11/10/2015 04:30 PM, zhanghailiang wrote:
> On 2015/11/10 15:35, Jason Wang wrote:
>>
>>
>> On 11/10/2015 01:26 PM, Tkid wrote:
>>> Hi,all
>>>
>>> We are planning to reimplement colo proxy in userspace (Here is in
>>> qemu) to
>>> cache and compare net packets.This module is one of the importa
> - What's the plan for vhost? Userspace network in qemu is rather slow, most
> user will choose vhost.
[Dong, Eddie] Hi Jason:
How about we take staging approach? In general, COLO opens a door of
high performance HA solution, but it will take very long time to make
everything perfect. As
* Tkid (zhangchen.f...@cn.fujitsu.com) wrote:
> Hi,all
>
> We are planning to reimplement colo proxy in userspace (Here is in qemu) to
> cache and compare net packets.This module is one of the important components
> of COLO project and now it is still in early stage, so any comments and
> feedback
* Jason Wang (jasow...@redhat.com) wrote:
>
>
> On 11/10/2015 01:26 PM, Tkid wrote:
> > Hi,all
> >
> > We are planning to reimplement colo proxy in userspace (Here is in
> > qemu) to
> > cache and compare net packets.This module is one of the important
> > components
> > of COLO project and now i
On 11/10/2015 03:35 PM, Jason Wang wrote:
On 11/10/2015 01:26 PM, Tkid wrote:
Hi,all
We are planning to reimplement colo proxy in userspace (Here is in
qemu) to
cache and compare net packets.This module is one of the important
components
of COLO project and now it is still in early stage, so
On 2015/11/10 15:35, Jason Wang wrote:
On 11/10/2015 01:26 PM, Tkid wrote:
Hi,all
We are planning to reimplement colo proxy in userspace (Here is in
qemu) to
cache and compare net packets.This module is one of the important
components
of COLO project and now it is still in early stage, so any
On 11/10/2015 01:26 PM, Tkid wrote:
> Hi,all
>
> We are planning to reimplement colo proxy in userspace (Here is in
> qemu) to
> cache and compare net packets.This module is one of the important
> components
> of COLO project and now it is still in early stage, so any comments and
> feedback are
Hi,all
We are planning to reimplement colo proxy in userspace (Here is in qemu) to
cache and compare net packets.This module is one of the important components
of COLO project and now it is still in early stage, so any comments and
feedback are warmly welcomed,thanks in advance.
## Background
CO
On 07/31/2015 09:28 AM, zhanghailiang wrote:
On 2015/7/31 9:08, Yang Hongyang wrote:
On 07/31/2015 01:53 AM, Dr. David Alan Gilbert wrote:
* Yang Hongyang (yan...@cn.fujitsu.com) wrote:
On 07/30/2015 09:59 PM, Dr. David Alan Gilbert wrote:
* zhanghailiang (zhang.zhanghaili...@huawei.com)
On 2015/7/31 9:08, Yang Hongyang wrote:
On 07/31/2015 01:53 AM, Dr. David Alan Gilbert wrote:
* Yang Hongyang (yan...@cn.fujitsu.com) wrote:
On 07/30/2015 09:59 PM, Dr. David Alan Gilbert wrote:
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
On 2015/7/30 20:30, Dr. David Alan Gil
On 2015/7/31 1:53, Dr. David Alan Gilbert wrote:
* Yang Hongyang (yan...@cn.fujitsu.com) wrote:
On 07/30/2015 09:59 PM, Dr. David Alan Gilbert wrote:
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
On 2015/7/30 20:30, Dr. David Alan Gilbert wrote:
* Gonglei (arei.gong...@huawei.com)
On 07/31/2015 01:53 AM, Dr. David Alan Gilbert wrote:
* Yang Hongyang (yan...@cn.fujitsu.com) wrote:
On 07/30/2015 09:59 PM, Dr. David Alan Gilbert wrote:
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
On 2015/7/30 20:30, Dr. David Alan Gilbert wrote:
* Gonglei (arei.gong...@huaw
* Yang Hongyang (yan...@cn.fujitsu.com) wrote:
>
>
> On 07/30/2015 09:59 PM, Dr. David Alan Gilbert wrote:
> >* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
> >>On 2015/7/30 20:30, Dr. David Alan Gilbert wrote:
> >>>* Gonglei (arei.gong...@huawei.com) wrote:
> On 2015/7/30 19:56, Dr.
On 07/30/2015 09:59 PM, Dr. David Alan Gilbert wrote:
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
On 2015/7/30 20:30, Dr. David Alan Gilbert wrote:
* Gonglei (arei.gong...@huawei.com) wrote:
On 2015/7/30 19:56, Dr. David Alan Gilbert wrote:
* Jason Wang (jasow...@redhat.com) wro
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
> On 2015/7/30 20:30, Dr. David Alan Gilbert wrote:
> >* Gonglei (arei.gong...@huawei.com) wrote:
> >>On 2015/7/30 19:56, Dr. David Alan Gilbert wrote:
> >>>* Jason Wang (jasow...@redhat.com) wrote:
>
>
> On 07/30/2015 04:03 PM,
On 2015/7/30 20:30, Dr. David Alan Gilbert wrote:
* Gonglei (arei.gong...@huawei.com) wrote:
On 2015/7/30 19:56, Dr. David Alan Gilbert wrote:
* Jason Wang (jasow...@redhat.com) wrote:
On 07/30/2015 04:03 PM, Dr. David Alan Gilbert wrote:
* Dong, Eddie (eddie.d...@intel.com) wrote:
A quest
* Gonglei (arei.gong...@huawei.com) wrote:
> On 2015/7/30 19:56, Dr. David Alan Gilbert wrote:
> > * Jason Wang (jasow...@redhat.com) wrote:
> >>
> >>
> >> On 07/30/2015 04:03 PM, Dr. David Alan Gilbert wrote:
> >>> * Dong, Eddie (eddie.d...@intel.com) wrote:
> >> A question here, the packet co
On 2015/7/30 19:56, Dr. David Alan Gilbert wrote:
> * Jason Wang (jasow...@redhat.com) wrote:
>>
>>
>> On 07/30/2015 04:03 PM, Dr. David Alan Gilbert wrote:
>>> * Dong, Eddie (eddie.d...@intel.com) wrote:
>> A question here, the packet comparing may be very tricky. For example,
>> some prot
* Jason Wang (jasow...@redhat.com) wrote:
>
>
> On 07/30/2015 04:03 PM, Dr. David Alan Gilbert wrote:
> > * Dong, Eddie (eddie.d...@intel.com) wrote:
> A question here, the packet comparing may be very tricky. For example,
> some protocol use random data to generate unpredictable id or
On 07/30/2015 04:03 PM, Dr. David Alan Gilbert wrote:
> * Dong, Eddie (eddie.d...@intel.com) wrote:
A question here, the packet comparing may be very tricky. For example,
some protocol use random data to generate unpredictable id or
something else. One example is ipv6_select_ident(
* Dong, Eddie (eddie.d...@intel.com) wrote:
> > >
> > > A question here, the packet comparing may be very tricky. For example,
> > > some protocol use random data to generate unpredictable id or
> > > something else. One example is ipv6_select_ident() in Linux. So COLO
> > > needs a mechanism to ma
> >
> > A question here, the packet comparing may be very tricky. For example,
> > some protocol use random data to generate unpredictable id or
> > something else. One example is ipv6_select_ident() in Linux. So COLO
> > needs a mechanism to make sure PVM and SVM can generate same random
> data?
>
On 2015/7/30 12:23, Jason Wang wrote:
>
>
> On 07/20/2015 02:42 PM, Li Zhijian wrote:
>> Hi, all
>>
>> We are planning to implement colo-proxy in qemu to cache and compare
>> packets.
>> This module is one of the important component of COLO project and now
>> it is
>> still in early stage, so any
On 07/20/2015 02:42 PM, Li Zhijian wrote:
> Hi, all
>
> We are planning to implement colo-proxy in qemu to cache and compare
> packets.
> This module is one of the important component of COLO project and now
> it is
> still in early stage, so any comments and feedback are warmly welcomed,
> thank
On 2015-07-29 00:12, Samuel Thibault wrote:
> Hello,
>
> Jan Kiszka, le Mon 27 Jul 2015 15:33:27 +0200, a écrit :
>> Of course, I'm fine with handing this over to someone who'd like to
>> pick up. Do we have volunteers?
>>
>> Samuel, would you like to do this? As a subsystem maintainer, you are
>>
zhanghailiang, le Tue 21 Jul 2015 09:59:22 +0800, a écrit :
> I didn't find any news since that version, are you still trying to
> push them to qemu upstream ?
I'd still be trying if I had any actual answer other than "we need to
find time to deal about it" :)
I can rebase the patch series over t
Hello,
Jan Kiszka, le Mon 27 Jul 2015 15:33:27 +0200, a écrit :
> Of course, I'm fine with handing this over to someone who'd like to
> pick up. Do we have volunteers?
>
> Samuel, would you like to do this? As a subsystem maintainer, you are
> already familiar with QEMU processes.
I can help wit
* Jason Wang (jasow...@redhat.com) wrote:
>
>
> On 07/27/2015 01:51 PM, Yang Hongyang wrote:
> > On 07/27/2015 12:49 PM, Jason Wang wrote:
> >>
> >>
> >> On 07/27/2015 11:54 AM, Yang Hongyang wrote:
> >>>
> >>>
> >>> On 07/27/2015 11:24 AM, Jason Wang wrote:
>
>
> On 07/24/2015 04:
Hi Dave,
Thanks for the comments!
On 07/27/2015 06:40 PM, Dr. David Alan Gilbert wrote:
* Yang Hongyang (yan...@cn.fujitsu.com) wrote:
Hi Jason,
On 07/24/2015 10:12 AM, Jason Wang wrote:
On 07/24/2015 10:04 AM, Dong, Eddie wrote:
Hi Stefan:
Thanks for your comments!
On Mon, Ju
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2015-07-27 12:13, Stefan Hajnoczi wrote:
> On Tue, Jul 21, 2015 at 10:49:29AM +0100, Stefan Hajnoczi wrote:
>> On Tue, Jul 21, 2015 at 08:13:42AM +0200, Jan Kiszka wrote:
>>> On 2015-07-20 17:01, Stefan Hajnoczi wrote:
On Mon, Jul 20, 2015 at 2
Hello,
I'm just back from vacancy with no Internet access, so will answer
shortly :)
Samuel
On 2015/7/27 18:13, Stefan Hajnoczi wrote:
On Tue, Jul 21, 2015 at 10:49:29AM +0100, Stefan Hajnoczi wrote:
On Tue, Jul 21, 2015 at 08:13:42AM +0200, Jan Kiszka wrote:
On 2015-07-20 17:01, Stefan Hajnoczi wrote:
On Mon, Jul 20, 2015 at 2:12 PM, Vasiliy Tolstov wrote:
2015-07-20 14:55 GMT+03:
* Yang Hongyang (yan...@cn.fujitsu.com) wrote:
> Hi Jason,
>
> On 07/24/2015 10:12 AM, Jason Wang wrote:
> >
> >
> >On 07/24/2015 10:04 AM, Dong, Eddie wrote:
> >>Hi Stefan:
> >>Thanks for your comments!
> >>
> >>>On Mon, Jul 20, 2015 at 02:42:33PM +0800, Li Zhijian wrote:
> We are plannin
On Tue, Jul 21, 2015 at 10:49:29AM +0100, Stefan Hajnoczi wrote:
> On Tue, Jul 21, 2015 at 08:13:42AM +0200, Jan Kiszka wrote:
> > On 2015-07-20 17:01, Stefan Hajnoczi wrote:
> > > On Mon, Jul 20, 2015 at 2:12 PM, Vasiliy Tolstov
> > > wrote:
> > >> 2015-07-20 14:55 GMT+03:00 zhanghailiang
> > >
On 07/27/2015 04:06 PM, Jason Wang wrote:
On 07/27/2015 03:49 PM, Yang Hongyang wrote:
On 07/27/2015 03:37 PM, Jason Wang wrote:
On 07/27/2015 01:51 PM, Yang Hongyang wrote:
On 07/27/2015 12:49 PM, Jason Wang wrote:
On 07/27/2015 11:54 AM, Yang Hongyang wrote:
On 07/27/2015 11:24 AM,
On 07/27/2015 03:53 PM, Jason Wang wrote:
On 07/27/2015 01:51 PM, Yang Hongyang wrote:
On 07/27/2015 12:49 PM, Jason Wang wrote:
On 07/27/2015 11:54 AM, Yang Hongyang wrote:
On 07/27/2015 11:24 AM, Jason Wang wrote:
On 07/24/2015 04:04 PM, Yang Hongyang wrote:
Hi Jason,
On 07/24/201
On 07/27/2015 03:49 PM, Yang Hongyang wrote:
> On 07/27/2015 03:37 PM, Jason Wang wrote:
>>
>>
>> On 07/27/2015 01:51 PM, Yang Hongyang wrote:
>>> On 07/27/2015 12:49 PM, Jason Wang wrote:
On 07/27/2015 11:54 AM, Yang Hongyang wrote:
>
>
> On 07/27/2015 11:24 AM, Jason
On 07/27/2015 01:51 PM, Yang Hongyang wrote:
> On 07/27/2015 12:49 PM, Jason Wang wrote:
>>
>>
>> On 07/27/2015 11:54 AM, Yang Hongyang wrote:
>>>
>>>
>>> On 07/27/2015 11:24 AM, Jason Wang wrote:
On 07/24/2015 04:04 PM, Yang Hongyang wrote:
> Hi Jason,
>
> On 07/24/201
On 07/27/2015 03:37 PM, Jason Wang wrote:
On 07/27/2015 01:51 PM, Yang Hongyang wrote:
On 07/27/2015 12:49 PM, Jason Wang wrote:
On 07/27/2015 11:54 AM, Yang Hongyang wrote:
On 07/27/2015 11:24 AM, Jason Wang wrote:
On 07/24/2015 04:04 PM, Yang Hongyang wrote:
Hi Jason,
On 07/24/201
On 07/27/2015 01:51 PM, Yang Hongyang wrote:
> On 07/27/2015 12:49 PM, Jason Wang wrote:
>>
>>
>> On 07/27/2015 11:54 AM, Yang Hongyang wrote:
>>>
>>>
>>> On 07/27/2015 11:24 AM, Jason Wang wrote:
On 07/24/2015 04:04 PM, Yang Hongyang wrote:
> Hi Jason,
>
> On 07/24/201
On 07/27/2015 12:49 PM, Jason Wang wrote:
On 07/27/2015 11:54 AM, Yang Hongyang wrote:
On 07/27/2015 11:24 AM, Jason Wang wrote:
On 07/24/2015 04:04 PM, Yang Hongyang wrote:
Hi Jason,
On 07/24/2015 10:12 AM, Jason Wang wrote:
On 07/24/2015 10:04 AM, Dong, Eddie wrote:
Hi Stefan:
On 07/27/2015 11:54 AM, Yang Hongyang wrote:
>
>
> On 07/27/2015 11:24 AM, Jason Wang wrote:
>>
>>
>> On 07/24/2015 04:04 PM, Yang Hongyang wrote:
>>> Hi Jason,
>>>
>>> On 07/24/2015 10:12 AM, Jason Wang wrote:
On 07/24/2015 10:04 AM, Dong, Eddie wrote:
> Hi Stefan:
>
On 07/27/2015 11:24 AM, Jason Wang wrote:
On 07/24/2015 04:04 PM, Yang Hongyang wrote:
Hi Jason,
On 07/24/2015 10:12 AM, Jason Wang wrote:
On 07/24/2015 10:04 AM, Dong, Eddie wrote:
Hi Stefan:
Thanks for your comments!
On Mon, Jul 20, 2015 at 02:42:33PM +0800, Li Zhijian wrote:
On 07/24/2015 04:04 PM, Yang Hongyang wrote:
> Hi Jason,
>
> On 07/24/2015 10:12 AM, Jason Wang wrote:
>>
>>
>> On 07/24/2015 10:04 AM, Dong, Eddie wrote:
>>> Hi Stefan:
>>> Thanks for your comments!
>>>
On Mon, Jul 20, 2015 at 02:42:33PM +0800, Li Zhijian wrote:
> We are planning to
Hi Jason,
On 07/24/2015 10:12 AM, Jason Wang wrote:
On 07/24/2015 10:04 AM, Dong, Eddie wrote:
Hi Stefan:
Thanks for your comments!
On Mon, Jul 20, 2015 at 02:42:33PM +0800, Li Zhijian wrote:
We are planning to implement colo-proxy in qemu to cache and compare
packets.
I thought
On 07/24/2015 10:04 AM, Dong, Eddie wrote:
> Hi Stefan:
> Thanks for your comments!
>
>> On Mon, Jul 20, 2015 at 02:42:33PM +0800, Li Zhijian wrote:
>>> We are planning to implement colo-proxy in qemu to cache and compare
>> packets.
>>
>> I thought there is a kernel module to do that?
>
BTW, I felt it is better to be called as an agency, rather than a proxy. Any
comments from native speaker?
Thx Eddie
> Hi, all
>
> We are planning to implement colo-proxy in qemu to cache and compare
> packets.
> This module is one of the important component of COLO project and now it is
> s
Hi Stefan:
Thanks for your comments!
>
> On Mon, Jul 20, 2015 at 02:42:33PM +0800, Li Zhijian wrote:
> > We are planning to implement colo-proxy in qemu to cache and compare
> packets.
>
> I thought there is a kernel module to do that?
Yes, that is the previous solution the COLO
On Tue, Jul 21, 2015 at 08:13:42AM +0200, Jan Kiszka wrote:
> On 2015-07-20 17:01, Stefan Hajnoczi wrote:
> > On Mon, Jul 20, 2015 at 2:12 PM, Vasiliy Tolstov
> > wrote:
> >> 2015-07-20 14:55 GMT+03:00 zhanghailiang :
> >>> Agreed, besides, it is seemed that slirp is not supporting ipv6, we also
On 2015-07-20 17:01, Stefan Hajnoczi wrote:
> On Mon, Jul 20, 2015 at 2:12 PM, Vasiliy Tolstov wrote:
>> 2015-07-20 14:55 GMT+03:00 zhanghailiang :
>>> Agreed, besides, it is seemed that slirp is not supporting ipv6, we also
>>> have to supplement it.
>>
>>
>> patch for ipv6 slirp support some tim
On 2015/7/20 23:01, Stefan Hajnoczi wrote:
On Mon, Jul 20, 2015 at 2:12 PM, Vasiliy Tolstov wrote:
2015-07-20 14:55 GMT+03:00 zhanghailiang :
Agreed, besides, it is seemed that slirp is not supporting ipv6, we also
have to supplement it.
patch for ipv6 slirp support some times ago sended to
On Mon, Jul 20, 2015 at 2:12 PM, Vasiliy Tolstov wrote:
> 2015-07-20 14:55 GMT+03:00 zhanghailiang :
>> Agreed, besides, it is seemed that slirp is not supporting ipv6, we also
>> have to supplement it.
>
>
> patch for ipv6 slirp support some times ago sended to qemu list, but i
> don't know why i
2015-07-20 14:55 GMT+03:00 zhanghailiang :
> Agreed, besides, it is seemed that slirp is not supporting ipv6, we also
> have to supplement it.
patch for ipv6 slirp support some times ago sended to qemu list, but i
don't know why in not accepted.
--
Vasiliy Tolstov,
e-mail: v.tols...@selfip.ru
CC Wen Congyang
On 07/20/2015 06:32 PM, Stefan Hajnoczi wrote:
On Mon, Jul 20, 2015 at 02:42:33PM +0800, Li Zhijian wrote:
We are planning to implement colo-proxy in qemu to cache and compare packets.
I thought there is a kernel module to do that?
Why does the proxy need to be part of the QEM
On 2015/7/20 18:32, Stefan Hajnoczi wrote:
On Mon, Jul 20, 2015 at 02:42:33PM +0800, Li Zhijian wrote:
We are planning to implement colo-proxy in qemu to cache and compare packets.
I thought there is a kernel module to do that?
Yes, but we decided to re-implement it in userspace (Here is in
On Mon, Jul 20, 2015 at 02:42:33PM +0800, Li Zhijian wrote:
> We are planning to implement colo-proxy in qemu to cache and compare packets.
I thought there is a kernel module to do that?
Why does the proxy need to be part of the QEMU process? -netdev socket
or host network stack features allow y
Hi, all
We are planning to implement colo-proxy in qemu to cache and compare packets.
This module is one of the important component of COLO project and now it is
still in early stage, so any comments and feedback are warmly welcomed,
thanks in advance.
## Background
COLO FT/HA (COarse-grain LOck
63 matches
Mail list logo
