From: Fruhwirth Clemens <clemens-dated-1066221801.48ed@endorphin.org>
To: Christian Kujau <evil@g-house.de>
Cc: linux-kernel@vger.kernel.org, linux-crypto@nl.linux.org
Subject: Re: crypto benchmark results with 2.6.0-test6
Date: Sun, 5 Oct 2003 14:43:21 +0200 [thread overview]
Message-ID: <20031005124321.GA2529@leto2.endorphin.org> (raw)
In-Reply-To: <3F800BF8.3020800@g-house.de>
[-- Attachment #1: Type: text/plain, Size: 1623 bytes --]
On Sun, Oct 05, 2003 at 02:18:00PM +0200, Christian Kujau wrote:
> Sorry, took me a while to retest.
Thanks :)
> Fruhwirth Clemens schrieb:
> >would you like to benchmark
> >http://clemens.endorphin.org/patches/aes-i586-asm-2.6.0-test5.diff
>
> yes, i did so, results on:
> http://www.nerdbynature.de/bench/prinz/
Looks promising. But it's not going to be merged because of objections by
the cryptoapi maintainer.
> >http://clemens.endorphin.org/twofish-i586/ (experimential)
>
> uh, i guess this masm/windoze/elf32 stuff is too much for me, i could
> try, but don't have time to dig into this. but you could try my script,
> and run benchmarks on your machine too.
> but: how is this twofish optimization supposed to go into mainline
> anyway? one had to use a special compiling environment to compile a kernel?
It's not a patch, it's an add-on. I'm working on a gas version of the
assembler code so it can be merged, but it's far from being complete
(although it works).
> i set up these benchmarks for me too, because i needed to know what
> cipher is fast enough for my own use. usually i sticked to serpent, now
> aes-i586 looks quite good on this PC. i wonder if it will compile and so
> something on ppc32 too, but probably not. which is a pity, because my
> primary use of the cryptoloop is a ppc :-(
Well that's the cost of an assembler implementation ;) it's not portable.
Probably you can one of IBM's compilers to compile the cipher of your
choice. http://www-3.ibm.com/software/awdtools/ccompilers/ ... Rumours say
they're fast than gcc.
Regards, Clemens
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-05 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-04 10:41 crypto benchmark results with 2.6.0-test6 Fruhwirth Clemens
2003-10-05 12:18 ` Christian Kujau
2003-10-05 12:43 ` Fruhwirth Clemens [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-03 18:14 Christian Kujau
2003-10-04 5:08 ` Christian Kujau
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=20031005124321.GA2529@leto2.endorphin.org \
--to=clemens-dated-1066221801.48ed@endorphin.org \
--cc=evil@g-house.de \
--cc=linux-crypto@nl.linux.org \
--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