Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
OpenHarmony
Third Party Openssl
提交
4e52b984
T
Third Party Openssl
项目概览
OpenHarmony
/
Third Party Openssl
1 年多 前同步成功
通知
9
Star
18
Fork
1
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
T
Third Party Openssl
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
提交
4e52b984
编写于
3月 17, 2009
作者:
A
Andy Polyakov
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
aes-390x.pl: commentary update.
上级
e22b8648
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
5 addition
and
5 deletion
+5
-5
crypto/aes/asm/aes-s390x.pl
crypto/aes/asm/aes-s390x.pl
+5
-5
未找到文件。
crypto/aes/asm/aes-s390x.pl
浏览文件 @
4e52b984
...
...
@@ -35,11 +35,11 @@
#
# Add support for hardware AES192/256 and reschedule instructions to
# minimize/avoid Address Generation Interlock hazard and to favour
# dual-issue z10 pipeline. This gave ~25% improvement on z10
. The gain
#
should be larger on earlier CPUs, because being dual-issue z10 makes
# i
t improssible to eliminate the interlock condition, critial path is
#
not long enough. Yet z10 spends ~24 cycles per byte processed with
# 128-bit key.
# dual-issue z10 pipeline. This gave ~25% improvement on z10
and
#
almost 50% on z9. The gain is smaller on z10, because being dual-
# i
ssue z10 makes it improssible to eliminate the interlock condition:
#
critial path is not long enough. Yet it spends ~24 cycles per byte
#
processed with
128-bit key.
#
# Unlike previous version hardware support detection takes place only
# at the moment of key schedule setup, which is denoted in key->rounds.
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录