From: Or Gerlitz
Date: Tue, 5 Feb 2019 11:03:01 +0200
> Dave, I see a copy of the patch on patchworks [1] with status being
> not applicable, what is missing here? the patch should apply AFAIK.
> There was also another patch reviewed here by me and Saeed [2], not
> sure where it stands from your
On Wed, Jan 30, 2019 at 12:20 AM Saeed Mahameed wrote:
>
> On Mon, 2019-01-28 at 15:28 -0800, xiangxia.m@gmail.com wrote:
> > From: Tonghao Zhang
> >
> > When we offload tc filters to hardware, hardware flows can
> > be updated when mac of encap destination ip is changed.
> > But we ignore on
On Mon, 2019-01-28 at 15:28 -0800, xiangxia.m@gmail.com wrote:
> From: Tonghao Zhang
>
> When we offload tc filters to hardware, hardware flows can
> be updated when mac of encap destination ip is changed.
> But we ignore one case, that the mac of local encap ip can
> be changed too, so we sh
On Tue, Jan 29, 2019 at 8:05 PM wrote:
>
> From: Tonghao Zhang
>
> When we offload tc filters to hardware, hardware flows can
> be updated when mac of encap destination ip is changed.
> But we ignore one case, that the mac of local encap ip can
> be changed too, so we should also update them.
>
>
From: Tonghao Zhang
When we offload tc filters to hardware, hardware flows can
be updated when mac of encap destination ip is changed.
But we ignore one case, that the mac of local encap ip can
be changed too, so we should also update them.
To fix it, add route_dev in mlx5e_encap_entry struct to
