examples/ipsec-secgw: avoid logs in data path

Update error prints in data path to RTE_LOG_DP().
Error prints in fast path are not good for performance
as they slow down the application when few bad packets are
received.

Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
Acked-by: Akhil Goyal <gakhil@marvell.com>

diff --git a/examples/ipsec-secgw/ipsec_worker.c b/examples/ipsec-secgw/ipsec_worker.c
index 7419e85db2181b186ad33ef6e7414bc671fae96e..e9493c56ae210b94bd493b61c73c9d5ceecec91b 100644 (file)
--- a/examples/ipsec-secgw/ipsec_worker.c
+++ b/examples/ipsec-secgw/ipsec_worker.c
@@ -332,7 +332,8 @@ process_ipsec_ev_inbound(struct ipsec_ctx *ctx, struct route_table *rt,
                break;
 
        default:
-               RTE_LOG(ERR, IPSEC, "Unsupported packet type = %d\n", type);
+               RTE_LOG_DP(DEBUG, IPSEC_ESP, "Unsupported packet type = %d\n",
+                          type);
                goto drop_pkt_and_exit;
        }
 
@@ -570,7 +571,8 @@ classify_pkt(struct rte_mbuf *pkt, struct ipsec_traffic *t)
                t->ip6.pkts[(t->ip6.num)++] = pkt;
                break;
        default:
-               RTE_LOG(ERR, IPSEC, "Unsupported packet type = %d\n", type);
+               RTE_LOG_DP(DEBUG, IPSEC_ESP, "Unsupported packet type = %d\n",
+                          type);
                free_pkts(&pkt, 1);
                break;
        }