All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Kujau <evil@g-house.de>
To: Fruhwirth Clemens <clemens-dated-1066128091.d4fe@endorphin.org>
Cc: linux-kernel@vger.kernel.org, linux-crypto@nl.linux.org
Subject: Re: crypto benchmark results with 2.6.0-test6
Date: Sun, 05 Oct 2003 14:18:00 +0200	[thread overview]
Message-ID: <3F800BF8.3020800@g-house.de> (raw)
In-Reply-To: <20031004104131.GA1533@leto2.endorphin.org>

Sorry, took me a while to retest.

Fruhwirth Clemens schrieb:
> Hi,
> 
> 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/

> and
> 
> http://clemens.endorphin.org/twofish-i586/ (experimential) 
> 
> too? :)

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?

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 :-(

Thank you,
Christian.

-- 
BOFH excuse #349:

Stray Alpha Particles from memory packaging caused Hard Memory Error on 
Server.


  reply	other threads:[~2003-10-05 12:18 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 [this message]
2003-10-05 12:43   ` Fruhwirth Clemens
  -- 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=3F800BF8.3020800@g-house.de \
    --to=evil@g-house.de \
    --cc=clemens-dated-1066128091.d4fe@endorphin.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.