[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180605.103031.2043903448130876802.davem@davemloft.net>
Date: Tue, 05 Jun 2018 10:30:31 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: paulb@...lanox.com
Cc: jiri@...lanox.com, xiyou.wangcong@...il.com, jhs@...atatu.com,
netdev@...r.kernel.org, kliteyn@...lanox.com, roid@...lanox.com,
shahark@...lanox.com, markb@...lanox.com, ogerlitz@...lanox.com
Subject: Re: [PATCH net] net: sched: cls: Fix offloading when ingress dev
is vxlan
From: Paul Blakey <paulb@...lanox.com>
Date: Tue, 5 Jun 2018 11:04:03 +0300
> When using a vxlan device as the ingress dev, we count it as a
> "no offload dev", so when such a rule comes and err stop is true,
> we fail early and don't try the egdev route which can offload it
> through the egress device.
>
> Fix that by not calling the block offload if one of the devices
> attached to it is not offload capable, but make sure egress on such case
> is capable instead.
>
> Fixes: caa7260156eb ("net: sched: keep track of offloaded filters [..]")
> Reviewed-by: Roi Dayan <roid@...lanox.com>
> Acked-by: Jiri Pirko <jiri@...lanox.com>
> Signed-off-by: Paul Blakey <paulb@...lanox.com>
Applied and queued up for -stable, thanks.
Powered by blists - more mailing lists