projects
/
openssl.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
cee73df
)
Commentary update.
author
Andy Polyakov
<appro@openssl.org>
Tue, 3 May 2005 21:16:42 +0000
(21:16 +0000)
committer
Andy Polyakov
<appro@openssl.org>
Tue, 3 May 2005 21:16:42 +0000
(21:16 +0000)
crypto/rc4/asm/rc4-x86_64.pl
patch
|
blob
|
history
diff --git
a/crypto/rc4/asm/rc4-x86_64.pl
b/crypto/rc4/asm/rc4-x86_64.pl
index 89239400d4563bdc78aed903de109769e0e80f06..f96df377b5c791565a26181214abb8f8110d9bd8 100755
(executable)
--- a/
crypto/rc4/asm/rc4-x86_64.pl
+++ b/
crypto/rc4/asm/rc4-x86_64.pl
@@
-44,8
+44,10
@@
# improvement [I had to test it], while final Intel P4 performance
# achieves respectful 432MBps on 2.8GHz processor now. For reference.
# If executed on Xeon, current RC4_CHAR code-path is 2.7x faster than
# improvement [I had to test it], while final Intel P4 performance
# achieves respectful 432MBps on 2.8GHz processor now. For reference.
# If executed on Xeon, current RC4_CHAR code-path is 2.7x faster than
-# RC4_INT code-path. While if executed on Opteron, it's is only 25%
-# slower than the latter...
+# RC4_INT code-path. While if executed on Opteron, it's only 25%
+# slower slower than the RC4_INT one [meaning that if detecting CPU
+# is not desired, then RC4_CHAR code-path should be preferred, as it
+# provides better *all-round* performance].
$output=shift;
open STDOUT,"| $^X ../perlasm/x86_64-xlate.pl $output";
$output=shift;
open STDOUT,"| $^X ../perlasm/x86_64-xlate.pl $output";