Re: [PATCH net-next 8/8] net/mlx5e: Support adding ingress tc rule when egress device flag is set
From: Or Gerlitz <hidden>
Date: 2016-11-30 17:10:57
From: Or Gerlitz <hidden>
Date: 2016-11-30 17:10:57
On Wed, Nov 30, 2016 at 6:36 PM, John Fastabend [off-list ref] 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 in that first series the actual redirect action to a tunnel device was being ignore?
Does this series clean up that bit of software/hardware alignment.
If only the 1st series is applied, the kernel pieces are functional but with user-space manually putting the decap (tunnel key release) TC rule on the uplink device (tc tool -> UAPI --> tc core --> flower --> mlx5), but under real life use-case, the rule is put on shared-tunnel device, so this series adds on the prev one. Or.