Re: [dpdk-dev] [PATCH] net/failsafe: fix source port ID in Rx packets

2019-04-19 Thread Adrien Mazarguil
On Thu, Apr 18, 2019 at 04:06:31PM +0200, David Marchand wrote: > Hey Adrien, Hey David! > On Thu, Apr 18, 2019 at 3:12 PM Adrien Mazarguil > wrote: > > > When passed to the application, Rx packets retain the port ID value > > originally set by slave devices. Unfortunately these IDs have no mea

Re: [dpdk-dev] [PATCH] net/failsafe: fix source port ID in Rx packets

2019-04-18 Thread Adrien Mazarguil
On Thu, Apr 18, 2019 at 03:42:24PM +0100, Ferruh Yigit wrote: > On 4/18/2019 2:11 PM, Adrien Mazarguil wrote: > > When passed to the application, Rx packets retain the port ID value > > originally set by slave devices. Unfortunately these IDs have no meaning to > > applications, which are typically

Re: [dpdk-dev] [PATCH] net/failsafe: fix source port ID in Rx packets

2019-04-18 Thread Ferruh Yigit
On 4/18/2019 2:11 PM, Adrien Mazarguil wrote: > When passed to the application, Rx packets retain the port ID value > originally set by slave devices. Unfortunately these IDs have no meaning to > applications, which are typically unaware of their existence. > > This confuses those caring about the

Re: [dpdk-dev] [PATCH] net/failsafe: fix source port ID in Rx packets

2019-04-18 Thread Gaƫtan Rivet
On Thu, Apr 18, 2019 at 03:11:26PM +0200, Adrien Mazarguil wrote: > When passed to the application, Rx packets retain the port ID value > originally set by slave devices. Unfortunately these IDs have no meaning to > applications, which are typically unaware of their existence. > > This confuses th

Re: [dpdk-dev] [PATCH] net/failsafe: fix source port ID in Rx packets

2019-04-18 Thread David Marchand
Hey Adrien, On Thu, Apr 18, 2019 at 3:12 PM Adrien Mazarguil wrote: > When passed to the application, Rx packets retain the port ID value > originally set by slave devices. Unfortunately these IDs have no meaning to > applications, which are typically unaware of their existence. > > This confuse