Re: [dpdk-dev] [PATCH v2 14/15] ethdev: add physical port action to flow API

2018-04-09 Thread Adrien Mazarguil
On Sat, Apr 07, 2018 at 12:51:40PM +0300, Andrew Rybchenko wrote: > On 04/06/2018 04:25 PM, Adrien Mazarguil wrote: > > This patch adds the missing action counterpart to the PHY_PORT pattern > > item, that is, the ability to directly inject matching traffic into a > > physical port of the underlyin

Re: [dpdk-dev] [PATCH v2 14/15] ethdev: add physical port action to flow API

2018-04-07 Thread Andrew Rybchenko
On 04/06/2018 04:25 PM, Adrien Mazarguil wrote: This patch adds the missing action counterpart to the PHY_PORT pattern item, that is, the ability to directly inject matching traffic into a physical port of the underlying device. Does it mean that if it is applied on ingress (incoming packet fro

[dpdk-dev] [PATCH v2 14/15] ethdev: add physical port action to flow API

2018-04-06 Thread Adrien Mazarguil
This patch adds the missing action counterpart to the PHY_PORT pattern item, that is, the ability to directly inject matching traffic into a physical port of the underlying device. It breaks ABI compatibility for the following public functions: - rte_flow_copy() - rte_flow_create() - rte_flow_que