Re: [dpdk-dev] [PATCH 2/2] net/mlx5: panic when destroying a queue in use

2017-04-12 Thread Adrien Mazarguil
On Wed, Apr 12, 2017 at 05:48:40PM +0100, Ferruh Yigit wrote: > On 4/11/2017 4:21 PM, Nelio Laranjeiro wrote: > > Since the queue release API does not allow failures (return value is void) > > and the flow API does not allow a queue to be released as long as a flow > > rule depends on it, the only

Re: [dpdk-dev] [PATCH 2/2] net/mlx5: panic when destroying a queue in use

2017-04-12 Thread Ferruh Yigit
On 4/11/2017 4:21 PM, Nelio Laranjeiro wrote: > Since the queue release API does not allow failures (return value is void) > and the flow API does not allow a queue to be released as long as a flow > rule depends on it, the only rational decision to avoid undefined behavior > is to panic in this si

[dpdk-dev] [PATCH 2/2] net/mlx5: panic when destroying a queue in use

2017-04-11 Thread Nelio Laranjeiro
Since the queue release API does not allow failures (return value is void) and the flow API does not allow a queue to be released as long as a flow rule depends on it, the only rational decision to avoid undefined behavior is to panic in this situation. Signed-off-by: Nelio Laranjeiro Acked-by: A