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>,
leesioh <solee@os.korea.ac.kr>,
Andrea Arcangeli <aarcange@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH V7 2/2] ksm: replace jhash2 with xxhash
Date: Thu, 13 Sep 2018 21:24:49 +0000 [thread overview]
Message-ID: <29bdb865-9a85-59e0-395a-6b30a8663e5e@microsoft.com> (raw)
In-Reply-To: <20180913211923.7696-3-timofey.titovets@synesis.ru>
On 9/13/18 5:19 PM, Timofey Titovets wrote:
> From: Timofey Titovets <nefelim4ag@gmail.com>
>
> Replace jhash2 with xxhash.
>
> Perf numbers:
> Intel(R) Xeon(R) CPU E5-2420 v2 @ 2.20GHz
> 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
>
> As jhash2 always will be slower (for data size like PAGE_SIZE).
> Don't use it in ksm at all.
>
> 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.
>
> Thanks.
>
> Changes:
> v1 -> v2:
> - Move xxhash() to xxhash.h/c and separate patches
> v2 -> v3:
> - Move xxhash() xxhash.c -> xxhash.h
> - replace xxhash_t with 'unsigned long'
> - update kerneldoc above xxhash()
> v3 -> v4:
> - Merge xxhash/crc32 patches
> - Replace crc32 with crc32c (crc32 have same as jhash2 speed)
> - Add auto speed test and auto choice of fastest hash function
> v4 -> v5:
> - Pickup missed xxhash patch
> - Update code with compile time choicen xxhash
> - Add more macros to make code more readable
> - As now that only possible use xxhash or crc32c,
> on crc32c allocation error, skip speed test and fallback to xxhash
> - For workaround too early init problem (crc32c not avaliable),
> move zero_checksum init to first call of fastcall()
> - Don't alloc page for hash testing, use arch zero pages for that
> v5 -> v6:
> - Use libcrc32c instead of CRYPTO API, mainly for
> code/Kconfig deps Simplification
> - Add crc32c_available():
> libcrc32c will BUG_ON on crc32c problems,
> so test crc32c avaliable by crc32c_available()
> - Simplify choice_fastest_hash()
> - Simplify fasthash()
> - struct rmap_item && stable_node have sizeof == 64 on x86_64,
> that makes them cache friendly. As we don't suffer from hash collisions,
> change hash type from unsigned long back to u32.
> - Fix kbuild robot warning, make all local functions static
> v6 -> v7:
> - Drop crc32c for now and use only xxhash in ksm.
>
> Signed-off-by: Timofey Titovets <nefelim4ag@gmail.com>
> Signed-off-by: leesioh <solee@os.korea.ac.kr>
Reviewed-by: Pavel Tatashin <pavel.tatashin@microsoft.com>
next prev parent reply other threads:[~2018-09-13 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 21:19 [PATCH V7 0/2] KSM replace hash algo " 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 [this message]
2018-09-13 21:26 ` Pasha Tatashin
2018-09-13 21:26 ` [PATCH V7 0/2] KSM replace hash algo " Pasha Tatashin
2018-09-13 21:34 ` 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=29bdb865-9a85-59e0-395a-6b30a8663e5e@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