Skip to content

Conversation

@vjabrayilov
Copy link
Collaborator

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

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 vjabrayilov force-pushed the blocking_recv branch 2 times, most recently from d0c35e7 to 6d26d6c Compare November 15, 2023 03:23
@vjabrayilov vjabrayilov force-pushed the blocking_recv branch 3 times, most recently from d805129 to 572e5dc Compare November 15, 2023 03:30
@sarsanaee sarsanaee added the enhancement New feature or request label Jan 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants