Re: [dpdk-dev] [PATCH] eal/ipc: stop async IPC loop on callback request

2018-04-10 Thread Tan, Jianfeng
On 4/10/2018 10:17 PM, Burakov, Anatoly wrote: On 10-Apr-18 2:53 PM, Tan, Jianfeng wrote: On 4/10/2018 6:03 PM, Anatoly Burakov wrote: EAL did not stop processing further asynchronous requests on encountering a request that should trigger the callback. This resulted in erasing valid request

Re: [dpdk-dev] [PATCH] eal/ipc: stop async IPC loop on callback request

2018-04-10 Thread Burakov, Anatoly
On 10-Apr-18 2:53 PM, Tan, Jianfeng wrote: On 4/10/2018 6:03 PM, Anatoly Burakov wrote: EAL did not stop processing further asynchronous requests on encountering a request that should trigger the callback. This resulted in erasing valid requests but not triggering them. That means one wakeup

Re: [dpdk-dev] [PATCH] eal/ipc: stop async IPC loop on callback request

2018-04-10 Thread Tan, Jianfeng
On 4/10/2018 6:03 PM, Anatoly Burakov wrote: EAL did not stop processing further asynchronous requests on encountering a request that should trigger the callback. This resulted in erasing valid requests but not triggering them. That means one wakeup could process multiple replies, and followi

[dpdk-dev] [PATCH] eal/ipc: stop async IPC loop on callback request

2018-04-10 Thread Anatoly Burakov
EAL did not stop processing further asynchronous requests on encountering a request that should trigger the callback. This resulted in erasing valid requests but not triggering them. Fix this by stopping the loop once we have a request that we can trigger. Also, remove unnecessary check for trigge