You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/**
* Guarantees that the specified @ref ucp_am_recv_callback_t callback,
* will always be called with @ref UCP_AM_RECV_ATTR_FLAG_DATA flag set,
* so the data will be accessible outside the callback, until
* @ref ucp_am_data_release is called.
*/
UCP_AM_FLAG_PERSISTENT_DATA = UCS_BIT(1)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
If setting
ucp_worker_set_am_recv_handlerwith theparam.flags = UCP_AM_FLAG_PERSISTENT_DATA, in theucp_am_recv_callback_tfunction, will theucp_am_recv_param_talways be setparam.flagswithUCP_AM_RECV_ATTR_FLAG_DATAflags and withoutUCP_AM_RECV_ATTR_FLAG_RNDV?If so, does it mean that rndv protocol won't work when setting
ucp_worker_set_am_recv_handlerwith theparam.flags = UCP_AM_FLAG_PERSISTENT_DATAIf not, the
will always be called with @ref UCP_AM_RECV_ATTR_FLAG_DATA flag setin below sentence make me confused.Beta Was this translation helpful? Give feedback.
All reactions