mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: 14 Jun 2014 11:13:14 -0400	[thread overview]
Message-ID: <20140614151314.2721.qmail@ns.horizon.com> (raw)
In-Reply-To: <20140614111405.9630.qmail@ns.horizon.com>

Unfortunately, my test suite is not particularly lightweight.
Here are some figures (idle at full speed, and doing a parallel
kernel compile) for a 2.5 GHz Phenom.

Quite different numbers compared to the Ivy Bridge.  When the processor is
bust, fast_mix takes longer, instead.  And even the rolled up fast_mix2 is
(slightly) faster than the original fast_mix.  The 64-bit code is basically
the same speed as the 2x unrolled 32-bit code.

Presented in the same strange order as the Ivy Bridge, even though it's
not fastest-to-slowest this time.


Rolled up, 3x:
30748 5432	49066 24126
30583 6526	50271 23788
28621 4541	52966 25610
28017 3425	54181 25733
30425 5213	54441 25878
28556 3895	48969 26499
27853 3057	50813 25431
27471 2396	54065 27685
30328 5053	55931 27500
28702 3821	50811 24877

Unrolled, 3x:
26785 4278	40386 12695
25617 3302	41349 16593
25154 2357	41166 15904
24816 1886	40571 17449
27537 4927	41716 15723
28128 6657	42085 18098
25640 3410	41453 16486
25087 2199	39964 12193
27750 5384	38960 13672
26584 4699	38280 13697

Original:
35291 10362	82640 37663
32043 7848	81887 44853
32968 8994	80527 44847
31087 7207	84894 47535
29904 5602	81426 45401
34312 9824	54889 29060
36471 12948	65112 34232
31622 8539	63531 33871
31570 7745	57946 29070
30074 6116	62829 34393

Unrolled, 2x:
24491 2411	40335 16992
27644 6721	38981 16068
25473 4347	35260 10750
24784 3372	34211 10360
24326 2689	34178 11200
26404 4896	34498 10483
24905 3517	33793 10409
24107 2150	35321 11330
23968 1903	33818 11301
26254 4671	32728 9547

64-bit:
26877 7949	52258 25946
24862 5940	55765 27634
24528 5032	56568 28142
24844 5223	55007 27671
27115 8018	55754 27873
25504 6504	54286 27471
24772 5673	52717 26609
24427 4889	51362 27109
27219 8276	51431 22619
25640 6718	52835 26329

  reply	other threads:[~2014-06-14 15:13 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
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 [this message]
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=20140614151314.2721.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®