diff options
| author | zhanghailiang <zhang.zhanghailiang@huawei.com> | 2014-09-12 14:03:14 +0800 |
|---|---|---|
| committer | Michael Tokarev <mjt@tls.msk.ru> | 2014-09-20 17:55:53 +0400 |
| commit | 971ae6ef4772efe2adda3d773f334b9476ffa594 (patch) | |
| tree | 99b2395e92994998398b355d65b9ccc3e9890b9d /docs | |
| parent | 9d632f5f688e1cbb8ef9e54dfc671518dfe677aa (diff) | |
| download | qemu-971ae6ef4772efe2adda3d773f334b9476ffa594.zip qemu-971ae6ef4772efe2adda3d773f334b9476ffa594.tar.gz qemu-971ae6ef4772efe2adda3d773f334b9476ffa594.tar.bz2 | |
rdma: Fix incorrect description in comments
Since we have supported memory hotplug, VM's ram include pc.ram
and hotplug-memory.
Fix the confused description for rdma migration: pc.ram -> VM's ram
Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/rdma.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/rdma.txt b/docs/rdma.txt index 1f5d9e9..2bdd0a5 100644 --- a/docs/rdma.txt +++ b/docs/rdma.txt @@ -18,7 +18,7 @@ Contents: * RDMA Migration Protocol Description * Versioning and Capabilities * QEMUFileRDMA Interface -* Migration of pc.ram +* Migration of VM's ram * Error handling * TODO @@ -149,7 +149,7 @@ The only difference between a SEND message and an RDMA message is that SEND messages cause notifications to be posted to the completion queue (CQ) on the infiniband receiver side, whereas RDMA messages (used -for pc.ram) do not (to behave like an actual DMA). +for VM's ram) do not (to behave like an actual DMA). Messages in infiniband require two things: @@ -355,7 +355,7 @@ If the buffer is empty, then we follow the same steps listed above and issue another "QEMU File" protocol command, asking for a new SEND message to re-fill the buffer. -Migration of pc.ram: +Migration of VM's ram: ==================== At the beginning of the migration, (migration-rdma.c), |