On Thu, Oct 06, 2016 at 03:32:36PM +0100, Declan Doherty wrote: > On 07/09/16 13:28, Ilya Maximets wrote: > > This reverts commit 5b7bb2bda5519b7800f814df64d4e015282140e5. > > > > It is necessary to reconfigure all queues every time because configuration > > can be changed. > > > > Hey Ilya, this makes sense. I guess this was my original intention but I > missed this case in my review of the change. > > > For example, if we're reconfiguring bonding device with new memory pool, > > already configured queues will still use the old one. And if the old > > mempool be freed, application likely will panic in attempt to use > > freed mempool. > > > > This happens when we use the bonding device with OVS 2.6 while MTU > > reconfiguration: > > > > PANIC in rte_mempool_get_ops(): > > assert "(ops_index >= 0) && (ops_index < RTE_MEMPOOL_MAX_OPS_IDX)" failed > > > > Cc: <stable at dpdk.org> > > Signed-off-by: Ilya Maximets <i.maximets at samsung.com> > > --- > > Acked-by: Declan Doherty <declan.doherty at intel.com>
Applied to dpdk-next-net/rel_16_11 /Bruce
