On 04/24/2013 02:38 AM, Paolo Bonzini wrote:
Il 24/04/2013 01:53, Michael R. Hines ha scritto:
So, I started investigating the problem, and I noticed that whenever
I disabled the limits of max_size, the throughput went back to
the normal throughput (peak of 26 gbps).
So, rather than change the
Il 24/04/2013 01:53, Michael R. Hines ha scritto:
>
> So, I started investigating the problem, and I noticed that whenever
> I disabled the limits of max_size, the throughput went back to
> the normal throughput (peak of 26 gbps).
>
> So, rather than change the default max_size calculation for TC
On 04/23/2013 05:10 PM, Paolo Bonzini wrote:
Il 23/04/2013 03:55, mrhi...@linux.vnet.ibm.com ha scritto:
+chunk_start = ram_chunk_start(block, rdma->current_chunk);
+
+if (host_addr < chunk_start) {
+return 0;
+}
Useless if remaining from previous submissions.
Paolo
Ooo
On 04/23/2013 04:59 PM, Paolo Bonzini wrote:
Il 23/04/2013 03:55, mrhi...@linux.vnet.ibm.com ha scritto:
+static size_t qemu_rdma_get_max_size(QEMUFile *f, void *opaque,
+ uint64_t transferred_bytes,
+ uint64_t time_spent,
+
Il 23/04/2013 03:55, mrhi...@linux.vnet.ibm.com ha scritto:
> +chunk_start = ram_chunk_start(block, rdma->current_chunk);
> +
> +if (host_addr < chunk_start) {
> +return 0;
> +}
Useless if remaining from previous submissions.
Paolo
Il 23/04/2013 03:55, mrhi...@linux.vnet.ibm.com ha scritto:
> +static size_t qemu_rdma_get_max_size(QEMUFile *f, void *opaque,
> + uint64_t transferred_bytes,
> + uint64_t time_spent,
> + uin
From: "Michael R. Hines"
Code that does need to be visible is kept
well contained inside this file and this is the only
new additional file to the entire patch - good progress.
This file includes the entire protocol and interfaces
required to perform RDMA migration.
Also, the configure and Make