From: David Bouyeure <david.bouyeure@fraudbuster.mobi>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] net/mlx5: rte_flow_item_gtp restricted to GTPU
Date: Tue, 28 Dec 2021 15:56:49 +0100 [thread overview]
Message-ID: <5537fe65-9b3d-d745-557c-ae714ca33bc4@fraudbuster.mobi> (raw)
[-- 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 --]
next reply other threads:[~2021-12-28 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 14:56 David Bouyeure [this message]
-- 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5537fe65-9b3d-d745-557c-ae714ca33bc4@fraudbuster.mobi \
--to=david.bouyeure@fraudbuster.mobi \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).