Skip to content

Conversation

@tarcieri
Copy link
Member

Changes it from 9 back to 8, like it was in aes v0.8.

Anecdotally we've had some reports of better performance: #515

I also think an odd number of blocks just seems a bit unusual to me, and 8 blocks is what I've typically seen in other implementations.

@tarcieri tarcieri requested a review from newpavlov December 29, 2025 15:37
Changes it from 9 back to 8, like it was in `aes` v0.8.

Anecdotally we've had some reports of better performance: #515

I also think an odd number of blocks just seems a bit unusual to me,
and 8 blocks is what I've typically seen in other implementations.
@tarcieri tarcieri force-pushed the aes/x86-par-blocks-size-8 branch from d69a75a to 4b8ca5f Compare December 29, 2025 15:40
@newpavlov
Copy link
Member

I am not sure it will help with the performance issue, since IIUC it was caused by failed inlining. But I guess having a power-of-two block size could help with generating more efficient chunking code.

@newpavlov newpavlov merged commit 17bbd0b into master Jan 7, 2026
29 checks passed
@newpavlov newpavlov deleted the aes/x86-par-blocks-size-8 branch January 7, 2026 23:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants