On 07/17/2017 04:55 PM, Dr. David Alan Gilbert wrote:
* Zhang Chen (zhangchen.f...@cn.fujitsu.com) wrote:

On 07/14/2017 11:25 AM, Jason Wang wrote:

On 2017年07月13日 13:52, Zhang Chen wrote:
If primary packet's sequence number not same with secondary packet's
sequence number, no need to compare the packet other field.

Signed-off-by: Zhang Chen <zhangchen.f...@cn.fujitsu.com>
   net/colo-compare.c | 6 ++++++
   1 file changed, 6 insertions(+)

diff --git a/net/colo-compare.c b/net/colo-compare.c
index 0f8e198..2caeb80 100644
--- a/net/colo-compare.c
+++ b/net/colo-compare.c
@@ -222,6 +222,12 @@ static int colo_packet_compare_tcp(Packet
*spkt, Packet *ppkt)
       ptcp = (struct tcphdr *)ppkt->transport_header;
       stcp = (struct tcphdr *)spkt->transport_header;
   +    if ((ptcp->th_flags & TH_SYN) != TH_SYN &&
+        ptcp->th_seq != stcp->th_seq) {
+        trace_colo_compare_main("colo_packet_compare_tcp seq not
+        return -1;
+    }
        * The 'identification' field in the IP header is *very* random
        * it almost never matches.  Fudge this by ignoring differences in
Do we have any statistics numbers for this?
Rethink about this patch, I will remove it in next version and send a
patch in the future.
Because in FTP get test, primary guest send lots of packet differ to
secondary guest's,
the packet payload are not same, but the total payload are same.
Do you mean that the TCP stream is the same but the packet sizes are
different due to different fragmentation?

Yes, like that:
We send this payload: "1234567890".

pkt1 payload:"123"
pkt2 payload:"4567890"

pkt1 payload:"1234567890"

I think I have to buffer some packet's payload depend on sequence number for
Any idea about this?
The original COLO discussions ~2-3 years ago talked about performing TCP
reassembly and comparing the TCP stream; not a simple task.

But the version I worked with also had the rewrite of the sequence
numbers on the secondary to cause them to match even with the same
fragmentation - but that doesn't seem to be upstream yet.

In current qemu upstream we use filter-rewriter to rewrite the sequence
numbers on the secondary, but we can not avoid different fragmentation in two side. Any comments about guarantee the primary side and the secondary side have the same fragmentation?

Zhang Chen


Zhang Chen


Zhang Chen

Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK


Zhang Chen

Reply via email to