From: Andreas Steinmetz <ast@domdv.de>
To: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Need AES benchmark on Intel 64 bit
Date: Thu, 21 Apr 2005 14:28:54 +0200 [thread overview]
Message-ID: <42679C86.5050604@domdv.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 727 bytes --]
Hi,
can anybody help out? I don't have access to Intel 64 bit CPUs and need
some microbenchmark results on Intel 64 bit. Usage guide for the
attached archive:
'ref' contains the current generic AES implementation
'new' contains the 64 bit AES assembler implementation
Do 'make' in both directories and run the resulting 'aes' on an
otherwise idle system without any cpufreq (speedstep) stuff active.
Preferrably do multiple runs to assert that the results are usable (a
few ticks difference between runs are ok).
The microbenchmark is set up to produce somewhat real life results with
hot caches, thus the same data block is processed all the time.
--
Andreas Steinmetz SPAMmers use robotrap@domdv.de
[-- Attachment #2: microbench.tgz --]
[-- Type: application/x-tar-gz, Size: 6230 bytes --]
next reply other threads:[~2005-04-21 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 12:28 Andreas Steinmetz [this message]
2005-04-21 15:53 ` Need AES benchmark on Intel 64 bit Wes Felter
2005-04-21 17:33 ` Dave Jones
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=42679C86.5050604@domdv.de \
--to=ast@domdv.de \
--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