DPDK usage discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: "László Molnár" <laszlo.molnar@ericsson.com>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: mlx5: is GTP encapsulation possible using the rte_flow api?
Date: Mon, 22 Jul 2024 09:02:11 +0000	[thread overview]
Message-ID: <MN0PR12MB6056AB9102C8DAA1BE043909CFA82@MN0PR12MB6056.namprd12.prod.outlook.com> (raw)
In-Reply-To: <ZjuY+KquiSHG0bjo@elx-5cg22853xc>

[-- Attachment #1: Type: text/plain, Size: 1504 bytes --]

Hello,

> Hi All,

>I wonder whether it would be possible to implement HW accelerated GTP
>encapsulation (as a first step) functionality using a Bluefield 2 NIC
>and the rte_flow API?

yes should be supported.

>The encapsulation would need to work between different ports using
>hairpin queues.

>Let's say I already have the rules in dpdk-testpmd that remove the
>original ETH header using raw_decap, and add the new ETH/IP/UDP/GTP
>using raw_encap.

>Now I would need to update some header fields (payload length for
>pv4, udp, gtp). I would use "modify_field op add", but I found no way
>I can access the payload length field for UDP and GTP.

These are usually calculated by the NIC on ecnap so you don't need to set these fields or modify them.

>For example, when I try to access the UDP payload length field by using
>"dst_type udp_port_src dst_offset 32" in the "modify_field" action,
>I get a "destination offset is too big: Invalid argument" error.

In general and in MLX5 we don’t support changing the length field of the packet

>This seems to be caused by a check in the mlx5 driver, which is a bit
>surprising as the documentation in rte_flow.rst (DPDK version 24.03)
>says that:

   >``offset`` allows going past the specified packet field boundary to
   >copy a field to an arbitrary place in a packet,

>Is this just a driver limitation or an HW limitation? Or could a flex
>item solve this?

>Thanks, Laszlo

Kindest regards
Raslan Darawsheh

[-- Attachment #2: Type: text/html, Size: 6273 bytes --]

      parent reply	other threads:[~2024-07-22  9:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08 15:23 László Molnár
2024-07-22  5:43 ` Maayan Kashani
2024-07-22  9:02 ` Raslan Darawsheh [this message]

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=MN0PR12MB6056AB9102C8DAA1BE043909CFA82@MN0PR12MB6056.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=laszlo.molnar@ericsson.com \
    --cc=users@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).