OvS might invoke this API on its data path, out of sync
with its control plane. If the control path has already
deactivated the tunnel context entry, these invocations
will produce quite a few error printouts. Suppress that.
Fixes: 7e5b479803c3 ("net/sfc: implement control path operations in tunnel
offload")
Cc: sta...@dpdk.org
Signed-off-by: Ivan Malov <ivan.ma...@oktetlabs.ru>
Reviewed-by: Andrew Rybchenko <andrew.rybche...@oktetlabs.ru>
---
drivers/net/sfc/sfc_flow_tunnel.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/sfc/sfc_flow_tunnel.c
b/drivers/net/sfc/sfc_flow_tunnel.c
index e9eca90012..af5941c1ba 100644
--- a/drivers/net/sfc/sfc_flow_tunnel.c
+++ b/drivers/net/sfc/sfc_flow_tunnel.c
@@ -433,7 +433,7 @@ sfc_flow_tunnel_get_restore_info(struct rte_eth_dev *dev,
ft = &sa->flow_tunnels[ft_id];
if (ft->refcnt == 0) {
- sfc_err(sa, "tunnel offload: get_restore_info: tunnel=%u does
not exist",
+ sfc_dbg(sa, "tunnel offload: get_restore_info: tunnel=%u does
not exist",
ft_id);
rc = ENOENT;
goto fail;
--
2.30.2
