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.
Frame wakers can't be accessed concurrently, so thescratch that - MIRI is unhappy. I still believe they can't be accessed concurrently, but at least we're protected now. Performance didn't really change either so that's nice.spin::RwLock
around them is removed.cookie_factory
with my own small set of functions. These can panic instead of returningResult
but are guarded by the ethernet frame creation code checking buffer sizes.block_on
method: theoretical max perf up to 15M packets/sec or 120 MiB/sec on my Windows 11 5950X machine. Throughput with a real network interface will be a lot lower I imagine but it's nice to see we can get over the 100Mbit 100Base-T limit in contrived cases.