On Fri, May 19, 2017 at 04:37:31PM +0300, 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 of dpdk eth device or pci address.
Tha
-Original Message-
> From: ovs-dev-boun...@openvswitch.org [mailto:ovs-dev-
> boun...@openvswitch.org] On Behalf Of Ilya Maximets
> Sent: Friday, May 19, 2017 2:38 PM
> To: d...@openvswitch.org; Daniele Di Proietto ;
> Darrell Ball
> Cc: Ilya Maximets ; Heetae Ahn
>
> Sub
> > Billy
> >
> >> -Original Message-
> >> From: ovs-dev-boun...@openvswitch.org [mailto:ovs-dev-
> >> boun...@openvswitch.org] On Behalf Of Ilya Maximets
> >> Sent: Friday, May 19, 2017 2:38 PM
> >> To: d...@openvswitch.org; Daniele
ets
>> Sent: Friday, May 19, 2017 2:38 PM
>> To: d...@openvswitch.org; Daniele Di Proietto ;
>> Darrell Ball
>> Cc: Ilya Maximets ; Heetae Ahn
>>
>> Subject: [ovs-dev] [PATCH v4 2/3] netdev-dpdk: Fix device leak on port
>> deletion.
>>
>> Curr
mets ; Heetae Ahn
>
> Subject: [ovs-dev] [PATCH v4 2/3] netdev-dpdk: Fix device leak on port
> deletion.
>
> Currently, once created device in dpdk will exist forever even after del-port
> operation untill we manually call 'ovs-appctl netdev-dpdk/detach ',
> where
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
