[PATCH 09/18] Introduce event-tap.

2011-04-25 Thread OHMURA Kei
event-tap controls when to start FT transaction, and provides proxy functions to called from net/block devices. While FT transaction, it queues up net/block requests, and flush them when the transaction gets completed. Signed-off-by: OHMURA Kei ohmura@lab.ntt.co.jp Signed-off-by: Yoshiaki

[PATCH 09/18] Introduce event-tap.

2011-03-22 Thread Yoshiaki Tamura
event-tap controls when to start FT transaction, and provides proxy functions to called from net/block devices. While FT transaction, it queues up net/block requests, and flush them when the transaction gets completed. Signed-off-by: Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp Signed-off-by:

Re: [PATCH 09/18] Introduce event-tap.

2011-03-09 Thread ya su
Yoshi: I meet one problem if I killed a ft source VM, the dest ft VM will return errors as the following: qemu-system-x86_64: fill buffer failed, Resource temporarily unavailable qemu-system-x86_64: recv header failed the problem is that the dest VM can not continue to run, as it is

Re: [PATCH 09/18] Introduce event-tap.

2011-03-09 Thread Yoshiaki Tamura
ya su wrote: Yoshi: I meet one problem if I killed a ft source VM, the dest ft VM will return errors as the following: qemu-system-x86_64: fill buffer failed, Resource temporarily unavailable qemu-system-x86_64: recv header failed the problem is that the dest VM can not continue to

Re: [PATCH 09/18] Introduce event-tap.

2011-03-08 Thread Yoshiaki Tamura
ya su wrote: Yokshiaki: event-tap record block and io wirte events, and replay these on the other side, so block_save_live is useless during the latter ft phase, right? if so, I think it need to process the following code in block_save_live function: Actually no. It just replays the

Re: [PATCH 09/18] Introduce event-tap.

2011-03-08 Thread ya su
2011/3/8 Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp: ya su wrote: Yokshiaki:     event-tap record block and io wirte events, and replay these on the other side, so block_save_live is useless during the latter ft phase, right? if so, I think it need to process the following code in

Re: [PATCH 09/18] Introduce event-tap.

2011-03-08 Thread ya su
Yoshi: I think event-tap is a great idea, it remove the reading from disk which will increase ft effiency much better as your plan in later series. one question: IO read/write may dirty rams, but it is difficute to differ them from other dirty pages like caused by running of softwares,

Re: [PATCH 09/18] Introduce event-tap.

2011-03-08 Thread Yoshiaki Tamura
ya su wrote: Yoshi: I think event-tap is a great idea, it remove the reading from disk which will increase ft effiency much better as your plan in later series. one question: IO read/write may dirty rams, but it is difficute to differ them from other dirty pages like caused by

Re: [PATCH 09/18] Introduce event-tap.

2011-03-03 Thread ya su
Yokshiaki: event-tap record block and io wirte events, and replay these on the other side, so block_save_live is useless during the latter ft phase, right? if so, I think it need to process the following code in block_save_live function: if (stage == 1) { init_blk_migration(mon,

[PATCH 09/18] Introduce event-tap.

2011-02-23 Thread Yoshiaki Tamura
event-tap controls when to start FT transaction, and provides proxy functions to called from net/block devices. While FT transaction, it queues up net/block requests, and flush them when the transaction gets completed. Signed-off-by: Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp Signed-off-by:

[PATCH 09/18] Introduce event-tap.

2011-02-23 Thread Yoshiaki Tamura
event-tap controls when to start FT transaction, and provides proxy functions to called from net/block devices. While FT transaction, it queues up net/block requests, and flush them when the transaction gets completed. Signed-off-by: Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp Signed-off-by:

[PATCH 09/18] Introduce event-tap.

2011-02-10 Thread Yoshiaki Tamura
event-tap controls when to start FT transaction, and provides proxy functions to called from net/block devices. While FT transaction, it queues up net/block requests, and flush them when the transaction gets completed. Signed-off-by: Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp Signed-off-by: