* [dpdk-dev] net/mlx5: rte_flow_item_gtp restricted to GTPU
@ 2021-12-28 14:56 David Bouyeure
0 siblings, 0 replies; 2+ messages in thread
From: David Bouyeure @ 2021-12-28 14:56 UTC (permalink / raw)
To: dev
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
Hi everybody,
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).
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.
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.
Do you confirm that mlx5 rte_flow implementation is definitely ignoring
GTPC packets? And, if so, for which reason?
Thanks a lot.
Regards.
P.S: sorry for the previous nested message in '[dpdk-dev] [PATCH v3 1/3]
net/iavf: support GTPU inner IPv4 for FDIR
<http://inbox.dpdk.org/dev/495fe401-7b39-462c-a698-9d5ee4ded7c5@fraudbuster.mobi/T/#m5f73a4d29de1fdb13663b77940110f2f98ab6085>'
[-- Attachment #2: Type: text/html, Size: 1489 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* [dpdk-dev] net/mlx5: rte_flow_item_gtp restricted to GTPU
2021-03-26 14:29 ` [dpdk-dev] [PATCH v3 1/3] net/iavf: support GTPU inner IPv4 for FDIR Junfeng Guo
@ 2021-12-28 14:45 ` David Bouyeure
0 siblings, 0 replies; 2+ messages in thread
From: David Bouyeure @ 2021-12-28 14:45 UTC (permalink / raw)
To: dev
Hi everybody,
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).
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.
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.
Do you confirm that mlx5 rte_flow implementation is definitely ignoring
GTPC packets? And, if so, for which reason?
Thanks a lot.
Regards.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-12-28 14:56 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-12-28 14:56 [dpdk-dev] net/mlx5: rte_flow_item_gtp restricted to GTPU David Bouyeure
-- strict thread matches above, loose matches on Subject: below --
2021-03-26 10:42 [dpdk-dev] [PATCH v2 1/3] net/iavf: support GTPU inner IPv4 for FDIR Junfeng Guo
2021-03-26 14:29 ` [dpdk-dev] [PATCH v3 0/3] support GTPU inner IPv4/IPv6 for AVF FDIR Junfeng Guo
2021-03-26 14:29 ` [dpdk-dev] [PATCH v3 1/3] net/iavf: support GTPU inner IPv4 for FDIR Junfeng Guo
2021-12-28 14:45 ` [dpdk-dev] net/mlx5: rte_flow_item_gtp restricted to GTPU David Bouyeure
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).