Re: [ovs-dev] [PATCH 2/3] netdev-dpdk: Fix device leak on port deletion.

2017-05-12 Thread Ilya Maximets
Hi Darrell. Comments inline and I'm sorry for late responses once again. Best regards, Ilya Maximets. On 13.04.2017 00:28, Darrell Ball wrote: > > > On 4/3/17, 8:04 AM, "ovs-dev-boun...@openvswitch.org on behalf of Ilya > Maximets" i.maxim...@samsung.com> wrote: > > Currently, once crea

Re: [ovs-dev] [PATCH 2/3] netdev-dpdk: Fix device leak on port deletion.

2017-04-12 Thread Darrell Ball
On 4/3/17, 8:04 AM, "ovs-dev-boun...@openvswitch.org on behalf of Ilya Maximets" wrote: Currently, once created device in dpdk will exist forever even after del-port operation untill we manually call 'ovs-appctl netdev-dpdk/detach ', where is not the port's name but the name

Re: [ovs-dev] [PATCH 2/3] netdev-dpdk: Fix device leak on port deletion.

2017-04-03 Thread Aaron Conole
Ilya Maximets writes: > Currently, once created device in dpdk will exist forever > even after del-port operation untill we manually call > 'ovs-appctl netdev-dpdk/detach ', where is not > the port's name but the name of dpdk eth device or pci address. > > Few issues with current implementation:

[ovs-dev] [PATCH 2/3] netdev-dpdk: Fix device leak on port deletion.

2017-04-03 Thread Ilya Maximets
Currently, once created device in dpdk will exist forever even after del-port operation untill we manually call 'ovs-appctl netdev-dpdk/detach ', where is not the port's name but the name of dpdk eth device or pci address. Few issues with current implementation: 1. Different API for usua