-
Notifications
You must be signed in to change notification settings - Fork 22
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
Blocking receive support #21
Open
vjabrayilov
wants to merge
33
commits into
main
Choose a base branch
from
blocking_recv
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
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.
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
Vanilla implementation resulting in 2x latency increase per message
* Fullly working version * Temporary `posted` variable added to track number of `sem_post` calls; to be removed upon PR
Added `blocking` argument to recv related calls, when set(1) calling thread will block after a message available to receive
vjabrayilov
force-pushed
the
blocking_recv
branch
from
November 11, 2023 21:38
4aa5579
to
d4e8d1b
Compare
vjabrayilov
force-pushed
the
blocking_recv
branch
from
November 15, 2023 03:17
b173207
to
d30f620
Compare
vjabrayilov
force-pushed
the
blocking_recv
branch
2 times, most recently
from
November 15, 2023 03:23
d0c35e7
to
6d26d6c
Compare
vjabrayilov
force-pushed
the
blocking_recv
branch
3 times, most recently
from
November 15, 2023 03:30
d805129
to
572e5dc
Compare
vjabrayilov
force-pushed
the
blocking_recv
branch
from
November 15, 2023 03:32
572e5dc
to
2aac9f6
Compare
vjabrayilov
force-pushed
the
blocking_recv
branch
from
November 15, 2023 03:56
e30fb32
to
13cc7cf
Compare
Default to 100k RPS
To accommodate CPU pinning experiments
vjabrayilov
force-pushed
the
blocking_recv
branch
from
November 16, 2023 21:06
a59d94a
to
5c1b94f
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.
The caller thread of the
machnet_recv
function can choose whether to block or not.It contains optimizations to incur the least possible penalty on the stack side.
Best,
Vahab