| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
The performance impact is not measurable, as the compiler loads these variables
in xmm registers in unrolled loops anyway.
However, we avoid loading these sensitive keys onto the stack. This happens for
larger key schedules, where the register count is insufficient. If that key
material is not on the stack, we can avoid to wipe it explicitly after
crypto operations.
|
| |
|
|
|
|
| |
While the required members are aligned in the struct as required, on 32-bit
platforms the allocator aligns the structures itself to 8 bytes only. This
results in non-aligned struct members, and invalid memory accesses.
|
| |
|
|
|
| |
While associated data is usually not that large, in some specific cases
this can bring a significant performance boost.
|
| |
|
|
| |
Increases performance by another ~30%.
|
| |
|
|
| |
Increases overall performance by ~25%.
|
| |
|
|
|
| |
This gives not much more than ~5% increase in performance, but allows us to
improve further.
|
| |
|
