mac: Only use one CRC engine for Checker #183
Open
Conversation
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 probably never worked, but it certainly doesn't work right now
We don't need 4 crc engines for checking, we can use a single one, blank out the "invalid" data bytes and check it against a precomputed expected result
david-sawatzke
force-pushed
the
optimize_crc
branch
from
cf44a80 to
e6bfbf2
Compare
david-sawatzke
changed the title
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
As we have a certain crc value for a complete valid packet, additional 0 bytes lead to a predictable new crc value. Thus, for reception, we can only use a single, wide, engine and blank out the invalid bytes. Then compare it against a precomputed expected crc value for this last_be value.
To be certain that this works, add a test to verify it.
While using the test, I noticed that 16 bit support with last_be is completely broken.
64 bits also don't work with the test case, as a new packet can arrive which the old one isn't fully processed in checker, but this might not be a real issue on hardware.