-
Notifications
You must be signed in to change notification settings - Fork 423
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
Q: implementation of ucp_request_alloc #5991
Comments
Or in other words, is it possible for me now to use the worker mempool for request management? It would be quite convenient. |
need to pass your request by |
in order to use worker mempool, need to leave UCP_OP_ATTR_FIELD_REQUEST unset, then UCP send operation will allocate and return a request if needed. UCP_OP_ATTR_FLAG_NO_IMM_CMPL flag forces to always allocate request, even if completed in-place. |
Thanks! When I pass my own allocated request ( |
@yosefe sorry, disregard my previous post about canceling the request. That was my bug. |
Yes, it should be possible, and if not working it's a bug. Can you pls post backtrace of the segfault? |
@yosefe I cannot be entirely sure this is not somehow my fault, but so far I was unable to find any bug.
This is the stack from the core dump:
In the code I allocate a custom request and post an
and this a simplified callback
|
It seems like UCP is trying to put my allocated request into it's pool? |
Currently
ucp_request_alloc
is defined to always returnNULL
. I would like to use it to pass my requests to the new*_nbx
API. What is the preferred way to implement this on the user-side?The text was updated successfully, but these errors were encountered: