| commit | a97270ad5d6dd0382ecb4568674226c8463e59fb | |
| author | Dr. David Alan Gilbert <dgilbert@redhat.com> | |
| Mon, 20 Apr 2015 15:57:16 +0000 (20 16:57 +0100) | ||
| committer | Juan Quintela <quintela@redhat.com> | |
| Fri, 12 Jun 2015 04:54:02 +0000 (12 06:54 +0200) | ||
| tree | 273310d83a850db5ec696f92d0a3fe904e21b90f | treesnapshot (tar.gz zip) |
| parent | 73d9a7961ab1b083fb2095413a3bd091e35f4369 | commitdiff |
Rename RDMA structures to make destination clear
RDMA has two data types that are named confusingly;
RDMALocalBlock (pointed to indirectly by local_ram_blocks)
RDMARemoteBlock (pointed to by block in RDMAContext)
RDMALocalBlocks, as the name suggests is a data strucuture that
represents the RDMAable RAM Blocks on the current side of the migration
whichever that is.
RDMARemoteBlocks is always the shape of the RAMBlocks on the
destination, even on the destination.
Rename:
RDMARemoteBlock -> RDMADestBlock
context->'block' -> context->dest_blocks
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Reviewed-by: Michael R. Hines <mrhines@us.ibm.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
RDMA has two data types that are named confusingly;
RDMALocalBlock (pointed to indirectly by local_ram_blocks)
RDMARemoteBlock (pointed to by block in RDMAContext)
RDMALocalBlocks, as the name suggests is a data strucuture that
represents the RDMAable RAM Blocks on the current side of the migration
whichever that is.
RDMARemoteBlocks is always the shape of the RAMBlocks on the
destination, even on the destination.
Rename:
RDMARemoteBlock -> RDMADestBlock
context->'block' -> context->dest_blocks
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Reviewed-by: Michael R. Hines <mrhines@us.ibm.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
| migration/rdma.c | diffblobblamehistory |