-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gcm pager #1959
Merged
Merged
Gcm pager #1959
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
4ffc0cf
core: AES-GCM: import table based GF-mult
jenswi-linaro 41ffaaf
core: LTC provide some AES primitives
jenswi-linaro 87aea44
core: crypto: AES-GCM: remove tomcrypt.h dependency
jenswi-linaro 7d26c8f
core: arm64: crypto: AES-GCM: add internal key expansion
jenswi-linaro 48ac11a
core: crypto: AES-GCM: separate encryption key
jenswi-linaro ef1fc1b
core: crypto: AES-GCM: internal_aes_gcm_{enc,dec}()
jenswi-linaro 2164d0a
core: pager: use new aes-gcm implementation
jenswi-linaro File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why ARM64 only?
I understand you're copying code from
core/lib/libtomcrypt/src/ciphers/
(aes_armv8a_ce.c
andaes_modes_armv8a_ce_a64.S
) intocore/arch/arm/crypto/
(aes-gcm-ce.c
andghash-ce-core_a64.S
) to cut that dependency on LTC so that pager can use accelerated code. Two things:ghash-ce-core_a32.S
using code fromaes_modes_armv8a_ce_a32.S
(functionce_aes_sub()
) ?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
core/lib/libtomcrypt/src/ciphers/aes_modes_armv8a_ce_a32.S
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry I wasn't clear. In ARM64 we have an implementation with AES and GHASH fused, which gives a good speedup. In ARM32 we don't have such an implementation (yet, ever?) so instead we're using the AES API in the cryptolib.
What we could do, is to extract the CE AES implementation from LTC and supply it to LTC similarly to how GHASH is supplied. The advantage is that we can get rid of some redundancy and have easier access to the routines. This however is not in that scope of this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I've got it now.