summaryrefslogtreecommitdiffstats
path: root/net
diff options
context:
space:
mode:
authorIdo Schimmel <idosch@nvidia.com>2021-03-30 09:58:41 +0300
committerDavid S. Miller <davem@davemloft.net>2021-03-30 17:51:21 -0700
commit7866f265b824589f2cf45fce8bf82d152557bd7c (patch)
tree6b7ea04c41ae9bd47dad8f95244c15b32262c953 /net
parent65550f03e98b4dd9f5050ee8c463f30cae95ae90 (diff)
downloadlinux-7866f265b824589f2cf45fce8bf82d152557bd7c.tar.gz
linux-7866f265b824589f2cf45fce8bf82d152557bd7c.tar.bz2
linux-7866f265b824589f2cf45fce8bf82d152557bd7c.zip
mlxsw: spectrum_router: Only perform atomic nexthop bucket replacement when requested
When cleared, the 'force' parameter in nexthop bucket replacement notifications indicates that a driver should try to perform an atomic replacement. Meaning, only update the contents of the bucket if it is inactive. Since mlxsw only queries buckets' activity once every second, there is no point in trying an atomic replacement if the idle timer interval is smaller than 1 second. Currently, mlxsw ignores the original value of 'force' and will always try an atomic replacement if the idle timer is not smaller than 1 second. Fix this by taking the original value of 'force' into account and never promoting a non-atomic replacement to an atomic one. Fixes: 617a77f044ed ("mlxsw: spectrum_router: Add nexthop bucket replacement support") Reported-by: Colin Ian King <colin.king@canonical.com> Signed-off-by: Ido Schimmel <idosch@nvidia.com> Reviewed-by: Petr Machata <petrm@nvidia.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions