From: Pavel Tatashin <pasha.tatashin@oracle.com>
To: Timofey Titovets <nefelim4ag@gmail.com>
Cc: linux-mm@kvack.org, leesioh <solee@os.korea.ac.kr>,
Andrea Arcangeli <aarcange@redhat.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH V6 2/2 RESEND] ksm: replace jhash2 with faster hash
Date: Tue, 22 May 2018 16:22:42 -0400 [thread overview]
Message-ID: <20180522202242.otvdunkl75yfhkt4@xakep.localdomain> (raw)
In-Reply-To: <20180418193220.4603-3-timofey.titovets@synesis.ru>
Hi Timofey,
>
> 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
That is a very nice improvement over jhash2!
> Add function to autoselect hash algo on boot,
> based on hashing speed, like raid6 code does.
Are you aware of hardware where crc32c is slower compared to xxhash?
Perhaps always use crc32c when available?
> +
> +static u32 fasthash(const void *input, size_t length)
> +{
> +again:
> + switch (fastest_hash) {
> + case HASH_CRC32C:
> + return crc32c(0, input, length);
> + case HASH_XXHASH:
> + return xxhash(input, length, 0);
You are loosing half of 64-bit word in xxh64 case? Is this acceptable? May
be do one more xor: in 64-bit case in xxhash() do: (v >> 32) | (u32)v ?
> + default:
> + choice_fastest_hash();
> + /* The correct value depends on page size and endianness */
> + zero_checksum = fasthash(ZERO_PAGE(0), PAGE_SIZE);
> + goto again;
> + }
> +}
choice_fastest_hash() does not belong to fasthash(). We are loosing leaf
function optimizations if you keep it in this hot-path. Also, fastest_hash
should really be a static branch in order to avoid extra load and conditional
branch.
I think, crc32c should simply be used when it is available, and use xxhash
otherwise, the decision should be made in ksm_init()
Thank you,
Pavel
next prev parent reply other threads:[~2018-05-22 20:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 19:32 [PATCH V6 0/2 RESEND] KSM replace hash algo " Timofey Titovets
2018-04-18 19:32 ` [PATCH V6 1/2 RESEND] xxHash: create arch dependent 32/64-bit xxhash() Timofey Titovets
2018-04-18 19:32 ` [PATCH V6 2/2 RESEND] ksm: replace jhash2 with faster hash Timofey Titovets
2018-05-08 15:26 ` Claudio Imbrenda
2018-05-11 23:06 ` Timofey Titovets
2018-05-14 10:17 ` Claudio Imbrenda
2018-05-16 10:26 ` Timofey Titovets
2018-05-22 20:22 ` Pavel Tatashin [this message]
2018-05-23 13:45 ` Timofey Titovets
2018-05-23 14:24 ` Pavel Tatashin
2018-05-24 8:01 ` Timofey Titovets
2018-05-25 1:16 ` Pavel Tatashin
2018-05-26 20:25 ` [PATCH] " kbuild test robot
2018-05-26 21:06 ` kbuild test robot
2018-05-27 13:03 ` [PATCH V6 2/2 RESEND] " Mike Rapoport
2018-05-29 14:45 ` Pavel Tatashin
2018-06-07 8:58 ` Timofey Titovets
2018-06-07 11:52 ` Mike Rapoport
2018-06-08 1:29 ` Pavel Tatashin
2018-06-10 5:38 ` Mike Rapoport
2018-06-22 18:48 ` Pavel Tatashin
2018-06-25 8:48 ` Mike Rapoport
2018-09-13 10:35 ` Timofey Titovets
2018-09-13 18:01 ` Mike Rapoport
2018-09-13 18:10 ` Pasha Tatashin
-- strict thread matches above, loose matches on Subject: below --
2018-02-07 10:22 [PATCH V6 0/2 RESEND] KSM replace hash algo " Timofey Titovets
2018-02-07 10:22 ` [PATCH V6 2/2 RESEND] ksm: replace jhash2 " 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=20180522202242.otvdunkl75yfhkt4@xakep.localdomain \
--to=pasha.tatashin@oracle.com \
--cc=aarcange@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nefelim4ag@gmail.com \
--cc=solee@os.korea.ac.kr \
/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