Support faster send/recv by not notifying the other side #1039
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.
(this is a draft)
Introduce a new send variant called (
send_buffered()
), which doesn't notify receivers to avoid syscalls/context switches at the cost of increased latency.sometimes, it's not desirable to incur the potential futex wake syscall cost for each and every message send.
as far as i can tell, there is no way to do like this in the current api:
naming
I haven't decided yet.. considering
.recv()
,{try_,}send_{timeout_,}unnotified()
/{try_,}recv_{timeout_,}unnotified()
might be better.