UDP: Enable sending and receiving of per-packet options #59
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
badeend
force-pushed
the
udp-send-receive-metadata
branch
from
59bc4ca to
43e23e7
Compare
…hop-limit per packet.
badeend
force-pushed
the
udp-send-receive-metadata
branch
from
43e23e7 to
fb2a4fb
Compare
|
To be reevaluated after preview2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
Caveat: the following options are enabled unconditionally:
The primary goal of these changes is to kickstart WASI's UDP capabilities and enable workloads that we couldn't run before.
I doubt these 32-ish additional bytes are going to cause any performance issues for the average program, but if they ever do we can always add a "diet" version of
receivewithout these fields.Fixes #38