Re: [dpdk-dev] [PATCH 8/8] ipc: fix net/mlx5 memleak

2019-04-23 Thread Yongseok Koh
> On Apr 23, 2019, at 1:09 AM, Burakov, Anatoly > wrote: > > On 22-Apr-19 6:51 PM, Yongseok Koh wrote: >>> On Apr 17, 2019, at 7:44 AM, Herakliusz Lipiec >>> wrote: >>> >>> When sending multiple requests, rte_mp_request_sync >>> can succeed sending a few of those requests, but then >>> fail

Re: [dpdk-dev] [PATCH 8/8] ipc: fix net/mlx5 memleak

2019-04-23 Thread Burakov, Anatoly
On 22-Apr-19 6:51 PM, Yongseok Koh wrote: On Apr 17, 2019, at 7:44 AM, Herakliusz Lipiec wrote: When sending multiple requests, rte_mp_request_sync can succeed sending a few of those requests, but then fail on a later one and in the end return with rc=-1. The upper layers - e.g. device hotpl

Re: [dpdk-dev] [PATCH 8/8] ipc: fix net/mlx5 memleak

2019-04-22 Thread Yongseok Koh
> On Apr 17, 2019, at 7:44 AM, Herakliusz Lipiec > wrote: > > When sending multiple requests, rte_mp_request_sync > can succeed sending a few of those requests, but then > fail on a later one and in the end return with rc=-1. > The upper layers - e.g. device hotplug - currently > handles this

[dpdk-dev] [PATCH 8/8] ipc: fix net/mlx5 memleak

2019-04-17 Thread Herakliusz Lipiec
When sending multiple requests, rte_mp_request_sync can succeed sending a few of those requests, but then fail on a later one and in the end return with rc=-1. The upper layers - e.g. device hotplug - currently handles this case as if no messages were sent and no memory for response buffers was all