diff options
| author | Like Xu <like.xu@linux.intel.com> | 2019-02-20 13:27:26 +0800 |
|---|---|---|
| committer | Laurent Vivier <laurent@vivier.eu> | 2019-03-06 10:40:21 +0100 |
| commit | 806be3734c3c55357f15ab6548df86433f81859f (patch) | |
| tree | ba9f4e26502a7adf0e36f883fcbd3ec2b028cd70 /docs/rdma.txt | |
| parent | d80cf1eb2e87df3a9bfb226bcc7fb3a1aa858817 (diff) | |
doc: fix typos for documents in tree
Signed-off-by: Like Xu <like.xu@linux.intel.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Message-Id: <1550640446-18788-1-git-send-email-like.xu@linux.intel.com>
Signed-off-by: Laurent Vivier <laurent@vivier.eu>
Diffstat (limited to 'docs/rdma.txt')
| -rw-r--r-- | docs/rdma.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/rdma.txt b/docs/rdma.txt index e6f9902617..a86e992c84 100644 --- a/docs/rdma.txt +++ b/docs/rdma.txt @@ -30,7 +30,7 @@ of the significantly lower latency and higher throughput over TCP/IP. This is because the RDMA I/O architecture reduces the number of interrupts and data copies by bypassing the host networking stack. In particular, a TCP-based migration, under certain types of memory-bound workloads, may take a more -unpredicatable amount of time to complete the migration if the amount of +unpredictable amount of time to complete the migration if the amount of memory tracked during each live migration iteration round cannot keep pace with the rate of dirty memory produced by the workload. @@ -408,7 +408,7 @@ socket is broken during a non-RDMA based migration. TODO: ===== 1. Currently, 'ulimit -l' mlock() limits as well as cgroups swap limits - are not compatible with infinband memory pinning and will result in + are not compatible with infiniband memory pinning and will result in an aborted migration (but with the source VM left unaffected). 2. Use of the recent /proc/<pid>/pagemap would likely speed up the use of KSM and ballooning while using RDMA. |