New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add dgram
crate
#1764
Draft
evanrittenhouse
wants to merge
21
commits into
master
Choose a base branch
from
evanrittenhouse/dgram
base: master
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Add dgram
crate
#1764
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
evanrittenhouse
force-pushed
the
evanrittenhouse/dgram
branch
5 times, most recently
from
April 24, 2024 04:58
4b9b904
to
e1ae9c5
Compare
evanrittenhouse
force-pushed
the
evanrittenhouse/dgram
branch
from
April 24, 2024 05:17
e1ae9c5
to
7850f24
Compare
evanrittenhouse
force-pushed
the
evanrittenhouse/dgram
branch
from
April 24, 2024 14:48
9a0adbd
to
9ad7cc5
Compare
evanrittenhouse
force-pushed
the
evanrittenhouse/dgram
branch
from
April 24, 2024 14:56
9ad7cc5
to
6f1c5dd
Compare
evanrittenhouse
force-pushed
the
evanrittenhouse/dgram
branch
2 times, most recently
from
April 25, 2024 16:11
5921dc7
to
5636abb
Compare
evanrittenhouse
force-pushed
the
evanrittenhouse/dgram
branch
2 times, most recently
from
April 25, 2024 16:43
d39138b
to
8412ac7
Compare
evanrittenhouse
force-pushed
the
evanrittenhouse/dgram
branch
3 times, most recently
from
April 26, 2024 05:15
b973dc7
to
9fa335c
Compare
evanrittenhouse
force-pushed
the
evanrittenhouse/dgram
branch
from
April 26, 2024 16:04
9fa335c
to
38aa4c5
Compare
1) Remove Mio layer and replace it with a sync FD layer 2) Move RecvData, RecvMetrics, and StoreCmsgSettings to `lib`, since syscalls is private 3) Rework the signature of `recv_msg` to take a `StoreCmsgSettings` to allow applications to handle custom cmsgs
evanrittenhouse
force-pushed
the
evanrittenhouse/dgram
branch
from
May 2, 2024 14:08
8ea3dd9
to
cc10a34
Compare
evanrittenhouse
force-pushed
the
evanrittenhouse/dgram
branch
from
May 10, 2024 23:47
1b4ed63
to
e8b6134
Compare
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.
Overview
This PR adds a new crate for abstracting away direct interactions with cmsgs. It currently only contains implementations for Linux, but we can add multi-platform support when required.
Testing
Unit tests exist for basic functionality. As far as checking the success of GSO/GRO operations, I fired up a local server with a known GSO/GRO implementation. I then
strace
d 100 requests to the server onmaster
, filtering onsendmsg
/recvmsg
. Checking the number of syscalls, we see:I then substituted that GSO/GRO implementation with the one in this crate, and performed an identical test. The output is: