From: Joachim Fritschi <jfritschi@freenet.de>
To: linux-kernel@vger.kernel.org
Cc: herbert@gondor.apana.org.au, davem@davemloft.net
Subject: [RFC][PATCH 2/2] Twofish cipher x86_64-asm optimized
Date: Sun, 7 May 2006 11:57:03 +0200 [thread overview]
Message-ID: <200605071157.03362.jfritschi@freenet.de> (raw)
Implementation:
-----------------------
This code is based on the current linux twofish cipher c implementation. Only
the decrypt/encrypt routines were replaced by optimized assembler code. The
in-kernel code by Matthew Skala takes care of the keysetup and precomputation
of the sbox lookup tables.
I have eliminated stack use, tried to optimize the code as much as possible
and limit code size. The patch is similar to the existing aes assembler
implementation.
Testing:
-----------
The code passed the kernel test module and passed automated tests on a
dm-crypt volume reading/writing large files with alternating modules ( c /
assembler ) and comparing results. It is also running on my workstation for
over a week now.
Benchmarks:
-------------------
Performance on a dm-crypt volume increased about 47% while reading. With
256bit keylength its pretty close to the speed of the aes assembler version.
http://homepages.tu-darmstadt.de/~fritschi/twofish/output_20060426_175710_x86_64.html
The write performance in this benchmark was limited by the harddrive and not
the algorithm / system speed. Any suggestions how to benchmark the overall
speed accurately are welcome.
Patch:
----------
http://homepages.tu-darmstadt.de/~fritschi/twofish/twofish-x86_64-asm-2.6.17.diff
Please have a look, try, improve and criticise.
Regards,
Joachim
next reply other threads:[~2006-05-07 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-07 9:57 Joachim Fritschi [this message]
2006-05-07 10:38 ` [RFC][PATCH 2/2] Twofish cipher x86_64-asm optimized Andi Kleen
2006-05-07 12:33 ` Herbert Xu
2006-05-07 13:33 ` Joachim Fritschi
2006-05-07 12:47 ` Joachim Fritschi
2006-05-07 20:49 ` Joachim Fritschi
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=200605071157.03362.jfritschi@freenet.de \
--to=jfritschi@freenet.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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