My 32 bit host running on an intel core i3 box said: $ ./api/dirty-log-perf dirty-log-perf: 262144 slot pages / 262144 mem pages rip 804a74a rip 804a74a get dirty log: 51571 ns for 1 dirty pages rip 804a74a get dirty log: 81190 ns for 2 dirty pages rip 804a74a get dirty log: 66606 ns for 4 dirty pages rip 804a74a get dirty log: 60408 ns for 8 dirty pages rip 804a74a get dirty log: 46711 ns for 16 dirty pages rip 804a74a get dirty log: 83563 ns for 32 dirty pages rip 804a74a get dirty log: 74367 ns for 64 dirty pages rip 804a74a get dirty log: 87240 ns for 128 dirty pages rip 804a74a get dirty log: 140161 ns for 256 dirty pages rip 804a74a get dirty log: 191288 ns for 512 dirty pages rip 804a74a get dirty log: 981045 ns for 1024 dirty pages rip 804a74a get dirty log: 1000755 ns for 2048 dirty pages rip 804a74a get dirty log: 1122837 ns for 4096 dirty pages rip 804a74a get dirty log: 1362598 ns for 8192 dirty pages rip 804a74a get dirty log: 1202789 ns for 16384 dirty pages rip 804a74a get dirty log: 1598484 ns for 32768 dirty pages rip 804a74a get dirty log: 2456946 ns for 65536 dirty pages rip 804a74a get dirty log: 3366358 ns for 131072 dirty pages rip 804a74a get dirty log: 5634134 ns for 262144 dirty pages Takuya Yoshikawa (3): Add dirty logging performance test dirty-log-perf: Split guest memory into two slots dirty-log-perf: Take slot size from command line api/dirty-log-perf.cc | 144 +++++++++++++++++++++++++++++++++++++++++++++++++ config-x86-common.mak | 5 ++- 2 files changed, 148 insertions(+), 1 deletions(-) create mode 100644 api/dirty-log-perf.cc -- 1.7.5.4 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
