From: Artur Skawina <art.08.09@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 0/7] block-sha1: improved SHA1 hashing
Date: Sat, 08 Aug 2009 07:34:51 +0200 [thread overview]
Message-ID: <4A7D0E7B.3030601@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.01.0908072107170.3288@localhost.localdomain>
Linus Torvalds wrote:
>
> I think I have found a way to avoid the gcc crazyness.
>
> Lookie here:
>
> # TIME[s] SPEED[MB/s]
> rfc3174 5.094 119.8
> rfc3174 5.098 119.7
> linus 1.462 417.5
> linusas 2.008 304
> linusas2 1.878 325
> mozilla 5.566 109.6
> mozillaas 5.866 104.1
> openssl 1.609 379.3
> spelvin 1.675 364.5
> spelvina 1.601 381.3
> nettle 1.591 383.6
>
> notice? I outperform all the hand-tuned asm on 32-bit too. By quite a
> margin, in fact.
>
> Now, I didn't try a P4, and it's possible that it won't do that there, but
> the 32-bit code generation sure looks impressive on my Nehalem box. The
> magic? I force the stores to the 512-bit hash bucket to be done in order.
> That seems to help a lot.
I named it 'linusv':
P4/i686:
# TIME[s] SPEED[MB/s]
rfc3174 1.456 41.92
rfc3174 1.445 42.22
linus 0.5865 104.1
linusph 0.5643 108.2
linusv 0.3697 165.1
linusvph 0.3618 168.7
linusp4 0.4312 141.5
linusas 0.4091 149.2
linusas2 0.4364 139.9
mozilla 1.102 55.37
mozillaas 1.297 47.07
openssl 0.261 233.9
opensslb 0.2395 254.9
spelvin 0.2653 230
nettle 0.438 139.4
and when tuning for prescott:
linus 0.6544 93.27
linusph 0.6523 93.57
linusv 0.3439 177.5
linusvph 0.3547 172.1
linusp4 0.3585 170.3
so it isn't as fast as the openssl asm ones, but it does win
in the C category.
> I outperform all the hand-tuned asm on 32-bit too. By quite a
> margin, in fact.
I've inlined the byteswapping in 'opensslb', maybe that one will
do a bit better.
http://www.src.multimo.pl/YDpqIo7Li27O0L0h/sha1bench.tar.gz
artur
next prev parent reply other threads:[~2009-08-08 5:35 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 15:13 [PATCH 0/7] block-sha1: improved SHA1 hashing Linus Torvalds
2009-08-06 15:15 ` [PATCH 1/7] block-sha1: add new optimized C 'block-sha1' routines Linus Torvalds
2009-08-06 15:16 ` [PATCH 2/7] block-sha1: try to use rol/ror appropriately Linus Torvalds
2009-08-06 15:18 ` [PATCH 3/7] block-sha1: make the 'ntohl()' part of the first SHA1 loop Linus Torvalds
2009-08-06 15:20 ` [PATCH 4/7] block-sha1: re-use the temporary array as we calculate the SHA1 Linus Torvalds
2009-08-06 15:22 ` [PATCH 5/7] block-sha1: macroize the rounds a bit further Linus Torvalds
2009-08-06 15:24 ` [PATCH 6/7] block-sha1: Use '(B&C)+(D&(B^C))' instead of '(B&C)|(D&(B|C))' in round 3 Linus Torvalds
2009-08-06 15:25 ` [PATCH 7/7] block-sha1: get rid of redundant 'lenW' context Linus Torvalds
2009-08-06 18:25 ` [PATCH 2/7] block-sha1: try to use rol/ror appropriately Bert Wesarg
2009-08-06 17:22 ` [PATCH 0/7] block-sha1: improved SHA1 hashing Artur Skawina
2009-08-06 18:09 ` Linus Torvalds
2009-08-06 19:10 ` Artur Skawina
2009-08-06 19:41 ` Linus Torvalds
2009-08-06 20:08 ` Artur Skawina
2009-08-06 20:53 ` Linus Torvalds
2009-08-06 21:24 ` Linus Torvalds
2009-08-06 21:39 ` Artur Skawina
2009-08-06 21:52 ` Artur Skawina
2009-08-06 22:27 ` Linus Torvalds
2009-08-06 22:33 ` Linus Torvalds
2009-08-06 23:19 ` Artur Skawina
2009-08-06 23:42 ` Linus Torvalds
2009-08-06 22:55 ` Artur Skawina
2009-08-06 23:04 ` Linus Torvalds
2009-08-06 23:25 ` Linus Torvalds
2009-08-07 0:13 ` Linus Torvalds
2009-08-07 1:30 ` Artur Skawina
2009-08-07 1:55 ` Linus Torvalds
2009-08-07 0:53 ` Artur Skawina
2009-08-07 2:23 ` Linus Torvalds
2009-08-07 4:16 ` Artur Skawina
[not found] ` <alpine.LFD.2.01.0908071614310.3288@localhost.localdomain>
[not found] ` <4A7CBD28.6070306@gmail.com>
[not found] ` <4A7CBF47.9000903@gmail.com>
[not found] ` <alpine.LFD.2.01.0908071700290.3288@localhost.localdomain>
[not found] ` <4A7CC380.3070008@gmail.com>
2009-08-08 4:16 ` Linus Torvalds
2009-08-08 5:34 ` Artur Skawina [this message]
2009-08-08 17:10 ` Linus Torvalds
2009-08-08 18:12 ` Artur Skawina
2009-08-08 22:58 ` Artur Skawina
2009-08-08 23:36 ` Artur Skawina
-- strict thread matches above, loose matches on Subject: below --
2009-08-07 7:36 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=4A7D0E7B.3030601@gmail.com \
--to=art.08.09@gmail.com \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).