Messages in this thread | | | From | Andy Lutomirski <> | Date | Mon, 26 Jun 2017 18:36:46 -0700 | Subject | Re: [PATCH v3 08/10] x86/hyper-v: use hypercall for remote TLB flush |
| |
On Tue, May 23, 2017 at 5:36 AM, Vitaly Kuznetsov <vkuznets@redhat.com> wrote: > Andy Lutomirski <luto@kernel.org> writes: > >> >> Also, can you share the benchmark you used for these patches? > > I didn't do much while writing the patchset, mostly I was running the > attached dumb trasher (32 pthreads doing mmap/munmap). On a 16 vCPU > Hyper-V 2016 guest I get the following (just re-did the test with > 4.12-rc1): > > Before the patchset: > # time ./pthread_mmap ./randfile > > real 3m33.118s > user 0m3.698s > sys 3m16.624s > > After the patchset: > # time ./pthread_mmap ./randfile > > real 2m19.920s > user 0m2.662s > sys 2m9.948s > > K. Y.'s guys at Microsoft did additional testing for the patchset on > different Hyper-V deployments including Azure, they may share their > findings too.
I ran this benchmark on my big TLB patchset, mainly to make sure I didn't regress your test. I seem to have sped it up by 30% or so instead. I need to study this a little bit to figure out why to make sure that the reason isn't that I'm failing to do flushes I need to do.
| |