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.
.@ovn.org>; Darrell Ball
> <db...@vmware.com>
> Cc: Heetae Ahn <heetae82....@samsung.com>
> Subject: Re: [ovs-dev] [PATCH v4 2/3] netdev-dpdk: Fix device leak on port
> deletion.
>
> On 26.05.2017 16:38, O Mahony, Billy wrote:
> > Hi Ilya,
> >
>
9, 2017 2:38 PM
>> To: d...@openvswitch.org; Daniele Di Proietto <diproiet...@ovn.org>;
>> Darrell Ball <db...@vmware.com>
>> Cc: Ilya Maximets <i.maxim...@samsung.com>; Heetae Ahn
>> <heetae82@samsung.com>
>> Subject: [ovs-dev] [PATCH v4 2/3]
are.com>
> Cc: Ilya Maximets <i.maxim...@samsung.com>; Heetae Ahn
> <heetae82@samsung.com>
> 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-p
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
