Re: [PATCH net-next 8/8] net/mlx5e: Support adding ingress tc rule when egress device flag is set

2016-11-30 Thread Or Gerlitz
On Wed, Nov 30, 2016 at 6:36 PM, John Fastabend wrote: > I started to dig through these patches and the last series here, > >Re: [PATCH net-next 00/13] Mellanox 100G SRIOV offloads tunnel_key > set/release > Can you explain how these two are related? I'm guessing

Re: [PATCH net-next 8/8] net/mlx5e: Support adding ingress tc rule when egress device flag is set

2016-11-30 Thread John Fastabend
On 16-11-30 06:41 AM, Hadar Hen Zion wrote: > When ndo_setup_tc is called with an egress_dev flag set, it means that > the ndo call was executed on the mirred action (egress) device and not > on the ingress device. > > In order to support this kind of ndo_setup_tc call, and insert the > correct

[PATCH net-next 8/8] net/mlx5e: Support adding ingress tc rule when egress device flag is set

2016-11-30 Thread Hadar Hen Zion
When ndo_setup_tc is called with an egress_dev flag set, it means that the ndo call was executed on the mirred action (egress) device and not on the ingress device. In order to support this kind of ndo_setup_tc call, and insert the correct decap rule to the hardware, the uplink device on the same