[Top][All Lists]

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

Re: [Qemu-devel] [PATCH v11 14/15] rdma: introduce MIG_STATE_NONE and ch

From: Paolo Bonzini
Subject: Re: [Qemu-devel] [PATCH v11 14/15] rdma: introduce MIG_STATE_NONE and change MIG_STATE_SETUP state transition
Date: Tue, 25 Jun 2013 23:06:08 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130514 Thunderbird/17.0.6

Il 25/06/2013 22:56, Michael R. Hines ha scritto:
> I was wrong - this does require a protocol extension.
> This is because the RDMA transfers are asynchronous, and thus
> we cannot know in advance that it is safe to unregister the memory
> associated with each individual transfer before the transfer actually
> completes.
> While the destination currently uses the protocol to participate in
> *registering* the page, the destination does not participate in the
> RDMA transfers themselves, only the source does, and thus would
> require a new exchange of messages to block and instruct the
> destination to unpin the memory.

Yes, that's what I recalled too (really what mst told me :)).  Does it
need to be blocking though?  As long as the pinning is blocking, and
messages are processed in order, the source can proceed immediately
after sending an unpin message.  This assumes of course that the chunk
is not being transmitted, and I am not sure how easy the source can
determine that.


reply via email to

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