From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] AES i586-asm optimized
Date: 11 Sep 2003 22:14:47 GMT [thread overview]
Message-ID: <bjqs4n$u7c$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 3F6095B5.9010100@pobox.com
In article <3F6095B5.9010100@pobox.com>,
Jeff Garzik <jgarzik@pobox.com> wrote:
| Jari Ruusu wrote:
| > It uses classic Pentium instruction set. Speed optimized for my 300 MHz
| > Pentium-2 test box. Original Gladman version that I started with was pretty
| > fast but I was able to improve performance about 7% over original version.
| >
| > On my same 300 MHz P2 test box, assembler implementation is about twice as
| > fast as the mainline kernel C implementation.
|
|
| Neat. Consider me surprised, then ;-)
|
| Don't take my message as objection to the merge. I dunno what DaveM or
| JamesM thinks, but I definitely support merging patches like this. It
| provides a great example, if nothing else.
|
| Eventually I bet there will be issues about automatic algorithm
| selection: like the RAID5 code, which benchmarks all available
| algorithms, and selects the fastest one.
Didn't we just have this discussion? ;-) RAID5 benchmarks all available
code and then uses SSE2 or whatever because it doesn't plunk the
registers or cache or something... sorry, the details escape me, or the
sorry details escape me, or whatever.
BTW: I do agree with your point here, I'm using cryptoloop for some
stuff I'm doing, and while I never do enough disk i/o to care, this is a
good thing for the future. I'm using a PII-350, but next month I have to
add a P55C SMP machine, and will be doing much more crypto.
Thanks for asking for clarification, the patch looks better for it.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
prev parent reply other threads:[~2003-09-11 22:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 15:38 [PATCH] AES i586-asm optimized Fruhwirth Clemens
2003-09-10 16:17 ` Jeff Garzik
2003-09-10 17:06 ` Jari Ruusu
2003-09-11 15:33 ` Jeff Garzik
2003-09-11 22:14 ` bill davidsen [this message]
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='bjqs4n$u7c$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.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