From: "George Spelvin" <linux@horizon.com>
To: linux@horizon.com, tytso@mit.edu
Cc: hpa@linux.intel.com, linux-kernel@vger.kernel.org,
mingo@kernel.org, price@mit.edu
Subject: Re: random: Benchamrking fast_mix2
Date: 12 Jun 2014 07:18:50 -0400 [thread overview]
Message-ID: <20140612111850.26176.qmail@ns.horizon.com> (raw)
In-Reply-To: <20140612041318.11805.qmail@ns.horizon.com>
Ted, just as an example of a possible tweak, the following change seems
to sightly improve speed without reducing diffusion. (It now looks a
bit more like the Skein mix() function.)
I'll look for more even more efficient kernels. It appears that the
inital XOR is costing a lot; 8 memory fetches take a while. Spacing that
out a bit would help, but it having input partway through the round ends
up requiring a major surgery to my avalanche-measuring code.
These rotation constants aren't final, but tweaking them shouldn't affect
the speed.
IMHO *one* pass of this is as good as the current fast_mix, and two
are considerably better. Three achieve almost complete avalanche,
but aren't really necessary.
Since the pass is made of two identical halves, half-passes are also
possible. Either using only 2 rotate constants, or by unrolling
the last half-pass.
// (29/66353) score = 49/121/123: 6 27 16 14
a += b; c += d;
+ b = rol32(a, 6); d = rol32(c, 27);
d ^= a; b ^= c;
- a = rol32(a, 15); c = rol32(c, 21);
a += b; c += d;
+ b = rol32(a, 16); d = rol32(c, 14);
d ^= a; b ^= c;
- a = rol32(a, 3); c = rol32(c, 7);
Of course, using wider words works fantastically.
These constants give 76 bits if avalanche after 2 rounds,
essentially full after 3:
extern void fast_mix2(struct fast_pool *f, __u32 const input[4])
{
uint64_t a = ((uint64_t *)f->pool)[0] ^ ((uint64_t const *)input)[0];
uint64_t b = ((uint64_t *)f->pool)[1] ^ ((uint64_t const *)input)[1];
int i;
for (i = 0; i < 3; i++) {
a += b; b = rol64(b, 52);
b ^= a; a = rol64(a, 10);
a += b; b = rol64(b, 47);
b ^= a; a = rol64(a, 17);
}
((uint64_t *)f->pool)[0] = a;
((uint64_t *)f->pool)[1] = b;
f->count++;
}
And it measures as faster than fast_mix even with 3 rounds:
# ./perftest ./ted64
fast_mix: 499 fast_mix2: 430
fast_mix: 431 fast_mix2: 430
fast_mix: 510 fast_mix2: 419
fast_mix: 430 fast_mix2: 419
fast_mix: 430 fast_mix2: 419
fast_mix: 431 fast_mix2: 419
fast_mix: 431 fast_mix2: 430
fast_mix: 510 fast_mix2: 419
fast_mix: 510 fast_mix2: 431
fast_mix: 510 fast_mix2: 430
And with 2 it's even faster.
(But so is fast_mix; there appears to be
significant timing instability here.)
# ./perftest ./ted64
fast_mix: 430 fast_mix2: 306
fast_mix: 431 fast_mix2: 306
fast_mix: 442 fast_mix2: 306
fast_mix: 442 fast_mix2: 306
fast_mix: 442 fast_mix2: 306
fast_mix: 442 fast_mix2: 363
fast_mix: 442 fast_mix2: 306
fast_mix: 442 fast_mix2: 329
fast_mix: 408 fast_mix2: 306
fast_mix: 442 fast_mix2: 329
next prev parent reply other threads:[~2014-06-12 11:18 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 0:05 [RFC PATCH] drivers/char/random.c: Is reducing locking range like this safe? George Spelvin
2014-06-09 1:35 ` Theodore Ts'o
2014-06-09 2:10 ` George Spelvin
2014-06-09 2:18 ` George Spelvin
2014-06-09 4:03 ` George Spelvin
2014-06-09 9:23 ` George Spelvin
2014-06-09 13:34 ` Theodore Ts'o
2014-06-09 15:04 ` George Spelvin
2014-06-09 15:50 ` Theodore Ts'o
2014-06-09 16:11 ` George Spelvin
2014-06-10 0:20 ` drivers/char/random.c: more ruminations George Spelvin
2014-06-10 1:20 ` Theodore Ts'o
2014-06-10 3:10 ` George Spelvin
2014-06-10 15:25 ` Theodore Ts'o
2014-06-10 20:40 ` George Spelvin
2014-06-10 21:20 ` Theodore Ts'o
2014-06-11 0:10 ` George Spelvin
2014-06-11 2:08 ` Theodore Ts'o
2014-06-11 3:58 ` George Spelvin
2014-06-11 13:11 ` Theodore Ts'o
2014-06-12 0:42 ` George Spelvin
2014-06-12 1:03 ` H. Peter Anvin
2014-06-11 4:34 ` George Spelvin
2014-06-11 13:09 ` Theodore Ts'o
2014-06-11 2:21 ` Theodore Ts'o
2014-06-09 13:17 ` drivers/char/random.c: More futzing about George Spelvin
2014-06-11 16:38 ` Theodore Ts'o
2014-06-11 16:48 ` H. Peter Anvin
2014-06-11 19:25 ` Theodore Ts'o
2014-06-11 20:41 ` H. Peter Anvin
2014-06-12 0:44 ` H. Peter Anvin
2014-06-12 1:51 ` George Spelvin
2014-06-12 0:32 ` George Spelvin
2014-06-12 3:22 ` Theodore Ts'o
2014-06-12 4:13 ` random: Benchamrking fast_mix2 George Spelvin
2014-06-12 11:18 ` George Spelvin [this message]
2014-06-12 20:17 ` Theodore Ts'o
2014-06-12 20:46 ` Theodore Ts'o
2014-06-13 0:23 ` George Spelvin
2014-06-13 15:52 ` Theodore Ts'o
2014-06-14 2:10 ` George Spelvin
2014-06-14 3:06 ` Theodore Ts'o
2014-06-14 5:25 ` George Spelvin
2014-06-14 6:24 ` Theodore Ts'o
2014-06-14 8:03 ` George Spelvin
2014-06-14 11:14 ` George Spelvin
2014-06-14 15:13 ` George Spelvin
2014-06-14 16:33 ` Theodore Ts'o
2014-06-15 0:23 ` George Spelvin
2014-06-15 1:17 ` Theodore Ts'o
2014-06-15 6:58 ` George Spelvin
2014-06-15 13:01 ` Theodore Ts'o
2014-06-14 6:27 ` Theodore Ts'o
2014-06-14 4:55 ` [RFC] random: is the IRQF_TIMER test working as intended? George Spelvin
2014-06-14 6:43 ` Theodore Ts'o
2014-06-14 7:23 ` George Spelvin
2014-06-12 3:43 ` drivers/char/random.c: More futzing about George Spelvin
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=20140612111850.26176.qmail@ns.horizon.com \
--to=linux@horizon.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=price@mit.edu \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®