<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi everybody,
<br>
<br>
<br>
I've implemented some flows offloading through rte_flow, and I'm
just finding out that my GTPC packets aren't handled the same way
as my GTPU ones by a Mellanox
Connect-X6(FLEX_PARSER_PROFILE_ENABLE==3).
<br>
<br>
In others words, the GTP rules that I set are ignoring GTPC
packets. The DPDK api doc doesn't say anything about any
GTP-C/GTP-U distinction as far as I know, only that there's no way
to set some filter against a GTPv2(GTP-C) header.
<br>
<br>
There's a reference to RTE_GTPU_UDP_PORT in
dpdk.20.11.2/drivers/net/mlx5/mlx5_flow_dv.c::flow_dv_translate_item_gtp(),
and none to RTE_GTPC_UDP_PORT.
<br>
<br>
Do you confirm that mlx5 rte_flow implementation is definitely
ignoring GTPC packets? And, if so, for which reason?
<br>
<br>
<br>
Thanks a lot.
<br>
<br>
<br>
Regards. <br>
</p>
<p><br>
</p>
<p>P.S: sorry for the previous nested message in '<a
href="http://inbox.dpdk.org/dev/495fe401-7b39-462c-a698-9d5ee4ded7c5@fraudbuster.mobi/T/#m5f73a4d29de1fdb13663b77940110f2f98ab6085"
id="r5f73a4d29de1fdb13663b77940110f2f98ab6085">[dpdk-dev] [PATCH
v3 1/3] net/iavf: support GTPU inner IPv4 for FDIR</a>'</p>
</body>
</html>