-
Bug
-
Resolution: Fixed
-
P2
-
9, 10
-
b166
-
Not verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8179152 | 10 | Anthony Scarpino | P2 | Resolved | Fixed | b06 |
JDK-8242156 | 8u261 | Anthony Scarpino | P2 | Closed | Fixed | b02 |
JDK-8246990 | emb-8u261 | Anthony Scarpino | P2 | Resolved | Fixed | team |
The GCM mode of operation is essentially CTR mode with an additional operation that provides authenticity. That means that we can reuse parts of the CTR mode code in GCM. The benefit of this arrangement is that there is an intrinsic for AES/CTR that significantly improves the performance of this operation on systems with AES instructions. The current GCM code has a loop that invoked the AES intrinsic one block at a time. It would be much more efficient to invoke the AES/CTR intrinsic on the entire buffer.
- backported by
-
JDK-8179152 Use CounterMode intrinsic for AES/GCM
-
- Resolved
-
-
JDK-8246990 Use CounterMode intrinsic for AES/GCM
-
- Resolved
-
-
JDK-8242156 Use CounterMode intrinsic for AES/GCM
-
- Closed
-
- relates to
-
JDK-8178478 Better parallelize GCM
-
- Closed
-