Allow rdma_delete_block to work without the hash
commit03fcab38617ac9bcd6ed28cb1b6a0ecd8fb3bc82
authorDr. David Alan Gilbert <dgilbert@redhat.com>
Thu, 11 Jun 2015 17:17:24 +0000 (11 18:17 +0100)
committerJuan Quintela <quintela@redhat.com>
Tue, 7 Jul 2015 12:54:48 +0000 (7 14:54 +0200)
tree5b0b54886d5387ef9a2b9a58b3de3b163146307f
parent632e3a5cd812d6bbd38fd2f3ffc189ff5ea51926
Allow rdma_delete_block to work without the hash

In the next patch we remove the hash on the destination,
rdma_delete_block does two things with the hash which can be avoided:
  a) The caller passes the offset and rdma_delete_block looks it up
     in the hash; fixed by getting the caller to pass the block
  b) The hash gets recreated after deletion; fixed by making that
     conditional on the hash being initialised.

While this function is currently only used during cleanup, Michael
asked that we keep it general for future dynamic block registration
work.

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