A few of my yesterday's replies made no sense... Lesson learned: don't
reply to code review comments on a late friday evening :)
On 23-Mar-18 6:21 PM, Burakov, Anatoly wrote:
On 23-Mar-18 3:38 PM, Tan, Jianfeng wrote:
We do. However, we have to wait for *something* if there aren't any
asynchr
On 23-Mar-18 3:38 PM, Tan, Jianfeng wrote:
Hi Anatoly,
Two general comments firstly.
Q1. As I understand, malloc usage as an example, when a primary process
receives a request in rte_mp_handle thread, it will allocate memory, and
broadcast an async request to all secondary processes, and it w
Hi Anatoly,
Two general comments firstly.
Q1. As I understand, malloc usage as an example, when a primary process
receives a request in rte_mp_handle thread, it will allocate memory, and
broadcast an async request to all secondary processes, and it will
return immediately; then responses are
This API is similar to the blocking API that is already present,
but reply will be received in a separate callback by the caller.
Under the hood, we create a separate thread to deal with replies to
asynchronous requests, that will just wait to be notified by the
main thread, or woken up on a timer
4 matches
Mail list logo