From: Paul Mackerras <paulus@samba.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Edgar Toernig <froese@gmx.de>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Mozilla SHA1 implementation
Date: Fri, 22 Apr 2005 17:35:40 +1000 [thread overview]
Message-ID: <17000.43340.760901.175004@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0504211238150.2344@ppc970.osdl.org>
Linus Torvalds writes:
> Interestingly, the Mozilla SHA1 code is about twice as fast as the openssl
> code on my G5, and judging by the disassembly, it's because it's much
> simpler. I think the openssl people have unrolled all the loops totally,
> which tends to be a disaster on any half-way modern CPU. But hey, it could
> be something as simple as optimization flags too.
Which gcc version are you using?
I get the opposite result on my 2GHz G5: the Mozilla version does
45MB/s, the openssl version does 135MB/s, and my version does 218MB/s.
The time for a fsck-cache on a linux-2.6 tree (cache hot) is 8.0
seconds for the Mozilla version, 5.2 seconds for the openssl version,
and 4.4 seconds for my version.
Paul.
next prev parent reply other threads:[~2005-04-22 7:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 10:52 [PATCH] use gcrypt instead of libssl for hash Junichi Uekawa
2005-04-17 17:52 ` Linus Torvalds
2005-04-17 22:36 ` Junichi Uekawa
2005-04-18 3:58 ` Edgar Toernig
2005-04-21 19:48 ` Mozilla SHA1 implementation Linus Torvalds
2005-04-21 22:59 ` Edgar Toernig
2005-04-22 6:49 ` Paul Mackerras
2005-04-22 7:35 ` Paul Mackerras [this message]
2005-04-22 15:31 ` Linus Torvalds
2005-04-22 15:40 ` Linus Torvalds
2005-04-22 15:58 ` (anal) Q: Are there any coding styles or development guidelines? Klaus Robert Suetterlin
2005-04-22 17:50 ` Linus Torvalds
2005-04-22 20:29 ` Mozilla SHA1 implementation Daniel Barkalow
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=17000.43340.760901.175004@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=froese@gmx.de \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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).