Closed
Bug 1592869
Opened 5 years ago
Closed 5 years ago
Use NEON for ctr_xor
Categories
(NSS :: Libraries, enhancement, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
3.48
People
(Reporter: m_kato, Assigned: m_kato)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
This bench is on Amazon's arm64 instance (Cortex-A72). Using NEON for ctr_xor
, aes_ctr improves 30%-40%.
Before
# mode in symmkey opreps cxreps context op time(sec) thrgput
aes_ctr_d 2Gb 256 35M 0 0.000 10000.000 10.000 217Mb
# mode in symmkey opreps cxreps context op time(sec) thrgput
aes_ctr_e 2Gb 256 35M 0 0.000 10000.000 10.000 218Mb
After
# mode in symmkey opreps cxreps context op time(sec) thrgput
aes_ctr_d 2Gb 256 48M 0 0.000 10000.000 10.000 294Mb
# mode in symmkey opreps cxreps context op time(sec) thrgput
aes_ctr_e 2Gb 256 48M 0 0.000 10000.000 10.000 295Mb
Assignee | ||
Comment 1•5 years ago
|
||
Android/arm32 build uses NEON as default compiler option, and we don't support non-NEON device on Android, so it can use NEON as default even if Android/arm32.
Assignee | ||
Comment 2•5 years ago
|
||
Using NEON for ctr_xor, aes_ctr can improve 30%-40%i decode/encode time on Cortex-A72.
Updated•5 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P1
Comment 3•5 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → 3.48
You need to log in
before you can comment on or make changes to this bug.
Description
•