Sort destination RAMBlocks to be the same as the source
commite4d633207c129dc5b7d145240ac4a1997ef3902f
authorDr. David Alan Gilbert <dgilbert@redhat.com>
Thu, 11 Jun 2015 17:17:26 +0000 (11 18:17 +0100)
committerJuan Quintela <quintela@redhat.com>
Tue, 7 Jul 2015 12:54:49 +0000 (7 14:54 +0200)
tree2ecfac602d7a4ff7847ee02e9ef210b5f962e27a
parent760ff4bebc86d08b252809e0da7261c986d022ff
Sort destination RAMBlocks to be the same as the source

Use the order of incoming RAMBlocks from the source to record
an index number; that then allows us to sort the destination
local RAMBlock list to match the source.

Now that the RAMBlocks are known to be in the same order, this
simplifies the RDMA Registration step which previously tried to
match RAMBlocks based on offset (which isn't guaranteed to match).

Looking at the existing compress code, I think it was erroneously
relying on an assumption of matching ordering, which this fixes.

Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
migration/rdma.c
trace-events