Re: [dpdk-dev] [PATCH 0/5] improve tap behavior

2017-05-12 Thread Ferruh Yigit
On 4/18/2017 9:17 AM, Pascal Mazon wrote: > The tap does not behave properly in some cases. > > It is generally expected that a real device should be available once the > probing has been done. > > It is also better to check if an operation (here, setting MAC) is > mandatory before performing it.

[dpdk-dev] [PATCH 0/5] improve tap behavior

2017-04-18 Thread Pascal Mazon
The tap does not behave properly in some cases. It is generally expected that a real device should be available once the probing has been done. It is also better to check if an operation (here, setting MAC) is mandatory before performing it. Typically in cases where the remote netdevice is a VF w

Re: [dpdk-dev] [PATCH 0/5] improve tap behavior

2017-04-14 Thread Ferruh Yigit
On 4/14/2017 10:32 AM, Pascal Mazon wrote: > The tap does not behave properly in some cases. > > It is generally expected that a real device should be available once the > probing has been done. > > It is also better to check if an operation (here, setting MAC) is > mandatory before performing it

[dpdk-dev] [PATCH 0/5] improve tap behavior

2017-04-14 Thread Pascal Mazon
The tap does not behave properly in some cases. It is generally expected that a real device should be available once the probing has been done. It is also better to check if an operation (here, setting MAC) is mandatory before performing it. Typically in cases where the remote netdevice is a VF w