Re: [dpdk-dev] [PATCH v2] fbarray: fix attach deadlock

2019-03-29 Thread Thomas Monjalon
29/03/2019 11:42, Burakov, Anatoly: > On 29-Mar-19 9:52 AM, Darek Stojaczyk wrote: > > rte_fbarray_attach() currently locks its internal > > spinlock, but never releases it. Secondary processes > > won't even start if there is more than one fbarray > > to be attached to - the second rte_fbarray_att

Re: [dpdk-dev] [PATCH v2] fbarray: fix attach deadlock

2019-03-29 Thread Burakov, Anatoly
On 29-Mar-19 9:52 AM, Darek Stojaczyk wrote: rte_fbarray_attach() currently locks its internal spinlock, but never releases it. Secondary processes won't even start if there is more than one fbarray to be attached to - the second rte_fbarray_attach() would be just stuck. Fix it by releasing the

[dpdk-dev] [PATCH v2] fbarray: fix attach deadlock

2019-03-29 Thread Darek Stojaczyk
rte_fbarray_attach() currently locks its internal spinlock, but never releases it. Secondary processes won't even start if there is more than one fbarray to be attached to - the second rte_fbarray_attach() would be just stuck. Fix it by releasing the lock at the end of rte_fbarray_attach(). I beli