From: Shuo Wang <wangshuo47@huawei.com>
To: <hjl.tools@gmail.com>, <fweimer@redhat.com>, <libc-alpha@sourceware.org>
Cc: <hushiyuan@huawei.com>, <liqingqing3@huawei.com>
Subject: x86-64: memcpy performance reduce when running in virtual mechine
Date: Mon, 11 Jan 2021 22:32:10 +0800 [thread overview]
Message-ID: <20210111143210.21636-1-wangshuo47@huawei.com> (raw)
The performance of memcpy 1024 has recovered. However, there is performance
reduce in host. This is test result (cycle):
memcpy_10 memcpy_1k memcpy_10k memcpy_1m memcpy_10m
before backport 8 34 187 130848 2325409
after backport 8 34 182 515156 5282603
Performance improvement 0.00% 0.00% 2.67% -293.71% -127.17%
>* Shuo Wang:
>
>> The environment information is as follows:
>> [host]
>> - kernel version: 4.18.0
>> - glibc version: 2.28
>> - gcc version: 8.3.1
>> - qemu version: 2.12.0
>> - libvirtd version: 4.5.0
>
>Does your have a glibc a backport of this patch?
>
>commit d3c57027470b78dba79c6d931e4e409b1fecfc80
>Author: Patrick McGehearty <patrick.mcgehearty@oracle.com>
>Date: Mon Sep 28 20:11:28 2020 +0000
>
> Reversing calculation of __x86_shared_non_temporal_threshold
>
>Some hypervisors set the number of reported threads in CPUID to zero.
>
>Thanks,
>Florian
>--
>Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
>Commercial register: Amtsgericht Muenchen, HRB 153243,
>Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
next reply other threads:[~2021-01-11 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 14:32 Shuo Wang [this message]
2021-01-11 15:09 ` Florian Weimer
-- strict thread matches above, loose matches on Subject: below --
2021-01-11 8:41 Shuo Wang
2021-01-11 8:38 Shuo Wang
2021-01-11 9:06 ` Florian Weimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210111143210.21636-1-wangshuo47@huawei.com \
--to=wangshuo47@huawei.com \
--cc=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=hushiyuan@huawei.com \
--cc=libc-alpha@sourceware.org \
--cc=liqingqing3@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).