qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [RFC PATCH RDMA support v5: 03/12] comprehensive protoc


From: Michael R. Hines
Subject: Re: [Qemu-devel] [RFC PATCH RDMA support v5: 03/12] comprehensive protocol documentation
Date: Thu, 11 Apr 2013 11:01:50 -0400
User-agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2

You cannot write data in the pipeline because you do not have the
permissions to do so yet until the registrations in the pipeline have
completed and been received by the primary VM.

On 04/11/2013 10:50 AM, Paolo Bonzini wrote:
Il 11/04/2013 16:37, Michael S. Tsirkin ha scritto:
pg1 ->  pin -> req -> res -> rdma -> done
         pg2 ->  pin -> req -> res -> rdma -> done
                 pg3 -> pin -> req -> res -> rdma -> done
                        pg4 -> pin -> req -> res -> rdma -> done
                               pg4 -> pin -> req -> res -> rdma -> done

It's like a assembly line see?  So while software does the registration
roundtrip dance, hardware is processing rdma requests for previous
chunks.
Does this only affects the implementation, or also the wire protocol?
Does the destination have to be aware that the source is doing pipelining?

Paolo

Yes, the destination has to be aware. The destination has to acknowledge
all of the registrations in the pipeline *and* the primary-VM has to block
until all the registrations in the pipeline have been received.




reply via email to

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