[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 08/10] Rework ram block hash

From: Michael R. Hines
Subject: Re: [Qemu-devel] [PATCH 08/10] Rework ram block hash
Date: Tue, 19 May 2015 14:02:39 -0500
User-agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.6.0

On 05/19/2015 01:55 PM, Dr. David Alan Gilbert wrote:
I would like to keep the ramblock list directly addressable by hash
on both sides, because, as I mentioned earlier, we want as much
flexibility in registering RAMBlock memory as possible by being
able to add or delete arbitrary blocks int the list at anytime during
a migration.

I will try to get the patchset that allows anyone to register memory
for transfer out as soon as I can.
Hmm OK, I think I can rework that to regenerate the hash; it's a little
difficult without knowing how you're intending to use it.


We can use the RAMBlock name as a key to the hash, right?

I see a "future" where storage replication also uses RDMA,
(not that I'm volunteering to write it), but I don't want to
lose the ability for arbitrary QEMU callers to be able to
register/unregister ramblocks dynamically.

- Michae

reply via email to

[Prev in Thread] Current Thread [Next in Thread]