From: Pasha Tatashin <Pavel.Tatashin@microsoft.com>
To: Timofey Titovets <timofey.titovets@synesis.ru>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: "rppt@linux.vnet.ibm.com" <rppt@linux.vnet.ibm.com>,
Timofey Titovets <nefelim4ag@gmail.com>,
Andrea Arcangeli <aarcange@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
leesioh <solee@os.korea.ac.kr>
Subject: Re: [PATCH V7 0/2] KSM replace hash algo with xxhash
Date: Thu, 13 Sep 2018 21:26:37 +0000 [thread overview]
Message-ID: <93650ca3-dd72-ba84-49a3-7f383a0eb7e8@microsoft.com> (raw)
In-Reply-To: <20180913211923.7696-1-timofey.titovets@synesis.ru>
On 9/13/18 5:19 PM, Timofey Titovets wrote:
> From: Timofey Titovets <nefelim4ag@gmail.com>
>
> Currently used jhash are slow enough and replace it allow as to make KSM
> less cpu hungry.
>
> About speed (in kernel):
> ksm: crc32c hash() 12081 MB/s
> ksm: xxh64 hash() 8770 MB/s
> ksm: xxh32 hash() 4529 MB/s
> ksm: jhash2 hash() 1569 MB/s
>
> By sioh Lee tests (copy from other mail):
> Test platform: openstack cloud platform (NEWTON version)
> Experiment node: openstack based cloud compute node (CPU: xeon E5-2620 v3, memory 64gb)
> VM: (2 VCPU, RAM 4GB, DISK 20GB) * 4
> Linux kernel: 4.14 (latest version)
> KSM setup - sleep_millisecs: 200ms, pages_to_scan: 200
>
> Experiment process
> Firstly, we turn off KSM and launch 4 VMs.
> Then we turn on the KSM and measure the checksum computation time until full_scans become two.
>
> The experimental results (the experimental value is the average of the measured values)
> crc32c_intel: 1084.10ns
> crc32c (no hardware acceleration): 7012.51ns
> xxhash32: 2227.75ns
> xxhash64: 1413.16ns
> jhash2: 5128.30ns
>
> In summary, the result shows that crc32c_intel has advantages over all
> of the hash function used in the experiment. (decreased by 84.54% compared to crc32c,
> 78.86% compared to jhash2, 51.33% xxhash32, 23.28% compared to xxhash64)
> the results are similar to those of Timofey.
>
> But,
> use only xxhash for now, because for using crc32c,
> cryptoapi must be initialized first - that require some
> tricky solution to work good in all situations.
>
> So:
> - Fisrt patch implement compile time pickup of fastest implementation of xxhash
> for target platform.
> - Second replace jhash2 with xxhash
>
> Thanks.
>
> CC: Andrea Arcangeli <aarcange@redhat.com>
> CC: linux-mm@kvack.org
> CC: kvm@vger.kernel.org
> CC: leesioh <solee@os.korea.ac.kr>
>
> Timofey Titovets (2):
> xxHash: create arch dependent 32/64-bit xxhash()
> ksm: replace jhash2 with xxhash
>
> include/linux/xxhash.h | 23 +++++++++++++
> mm/Kconfig | 2 ++
> mm/ksm.c | 93 +++++++++++++++++++++++++++++++++++++++++++++++---
> 3 files changed, 114 insertions(+), 4 deletions(-)
This is wrong stat. ksm.c should not have any new lines at all.
next prev parent reply other threads:[~2018-09-13 21:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 21:19 Timofey Titovets
2018-09-13 21:19 ` [PATCH V7 1/2] xxHash: create arch dependent 32/64-bit xxhash() Timofey Titovets
2018-09-13 21:24 ` Pasha Tatashin
2018-09-13 21:19 ` [PATCH V7 2/2] ksm: replace jhash2 with xxhash Timofey Titovets
2018-09-13 21:24 ` Pasha Tatashin
2018-09-13 21:26 ` Pasha Tatashin
2018-09-13 21:26 ` Pasha Tatashin [this message]
2018-09-13 21:34 ` [PATCH V7 0/2] KSM replace hash algo " Timofey Titovets
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=93650ca3-dd72-ba84-49a3-7f383a0eb7e8@microsoft.com \
--to=pavel.tatashin@microsoft.com \
--cc=aarcange@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nefelim4ag@gmail.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=solee@os.korea.ac.kr \
--cc=timofey.titovets@synesis.ru \
/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