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.
#265 introduced a new optimization to use SIMD, however, I found it does not work in some cases recently. It requires the dst and the src to be non-overlapping at all (the case in the test), but we can only ensure that "dst and src does not overlap in first block size". (see code comment)
Another frustrating thing is that in the cipher.StreamReader scenario (the case in go-mc net package), dst and src are completely overlapping, meaning they are not subject to the optimization in #265. So this PR does not actually affect the performance for go-mc net/bot package users, since they do not ever got benefited from #265, they got benefited only from #256. See https://go.dev/src/crypto/cipher/io.go#L21
I may try to optimize decryption in overlapping cases later this year (focusing on parallelism), for now I will only make small fixes.