[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200529121222.4b68ce20@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
Date: Fri, 29 May 2020 12:12:54 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Saeed Mahameed <saeedm@...lanox.com>
Cc: "David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
Maor Dickman <maord@...lanox.com>,
Roi Dayan <roid@...lanox.com>
Subject: Re: [net 3/6] net/mlx5e: Remove warning "devices are not on same
switch HW"
On Thu, 28 May 2020 23:56:42 -0700 Saeed Mahameed wrote:
> From: Maor Dickman <maord@...lanox.com>
>
> On tunnel decap rule insertion, the indirect mechanism will attempt to
> offload the rule on all uplink representors which will trigger the
> "devices are not on same switch HW, can't offload forwarding" message
> for the uplink which isn't on the same switch HW as the VF representor.
>
> The above flow is valid and shouldn't cause warning message,
> fix by removing the warning and only report this flow using extack.
>
> Fixes: f3953003a66f ("net/mlx5e: Fix allowed tc redirect merged eswitch offload cases")
> Signed-off-by: Maor Dickman <maord@...lanox.com>
> Reviewed-by: Roi Dayan <roid@...lanox.com>
> Signed-off-by: Saeed Mahameed <saeedm@...lanox.com>
Fixes tag: Fixes: f3953003a66f ("net/mlx5e: Fix allowed tc redirect merged eswitch offload cases")
Has these problem(s):
- Target SHA1 does not exist
Powered by blists - more mailing lists