DPDK patches and discussions
 help / color / mirror / Atom feed
From: Vamsi Krishna Attunuru <vattunuru@marvell.com>
To: "orika@nvidia.com" <orika@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: DPDK rte flow raw encap & decap actions
Date: Wed, 15 Feb 2023 15:07:27 +0000	[thread overview]
Message-ID: <MWHPR18MB09422917327F58B02070304DA6A39@MWHPR18MB0942.namprd18.prod.outlook.com> (raw)
In-Reply-To: <MWHPR18MB094229E9AF81DC43EA7FBE13A6A29@MWHPR18MB0942.namprd18.prod.outlook.com>

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

Ping....

From: Vamsi Krishna Attunuru
Sent: Tuesday, February 14, 2023 2:22 PM
To: orika@nvidia.com; dev@dpdk.org
Subject: DPDK rte flow raw encap & decap actions

Hi Ori Kam & dpdk dev team,

For the below rte flow action types, the description sounds a bit confusing to me. Description says the data must start with ETH header up to the tunnel item. But the next following statement(that describes MPLSoGRE example) mentions data just holds layer 2 header. Same is described for raw_decap action also. Could you please elaborate on what exactly data must hold and the expected actual packet's header(before/after the action) for the example (MPLSoGRE) mentioned or for any other tunnel encap/decap types.

/**
* @warning
* @b EXPERIMENTAL: this structure may change without prior notice
*
* RTE_FLOW_ACTION_TYPE_RAW_ENCAP
*
* Raw tunnel end-point encapsulation data definition.
*
* The data holds the headers definitions to be applied on the packet.
* The data must start with ETH header up to the tunnel item header itself.
* When used right after RAW_DECAP (for decapsulating L3 tunnel type for
* example MPLSoGRE) the data will just hold layer 2 header.
*
* The preserve parameter holds which bits in the packet the PMD is not allowed
* to change, this parameter can also be NULL and then the PMD is allowed
* to update any field.
*
* size holds the number of bytes in @p data and @p preserve.
*/
struct rte_flow_action_raw_encap {
        uint8_t *data; /**< Encapsulation data. */
        uint8_t *preserve; /**< Bit-mask of @p data to preserve on output. */
        size_t size; /**< Size of @p data and @p preserve. */
};

/**
* @warning
* @b EXPERIMENTAL: this structure may change without prior notice
*
* RTE_FLOW_ACTION_TYPE_RAW_DECAP
*
* Raw tunnel end-point decapsulation data definition.
*
* The data holds the headers definitions to be removed from the packet.
* The data must start with ETH header up to the tunnel item header itself.
* When used right before RAW_DECAP (for encapsulating L3 tunnel type for
* example MPLSoGRE) the data will just hold layer 2 header.
*
* size holds the number of bytes in @p data.
*/
struct rte_flow_action_raw_decap {
        uint8_t *data; /**< Encapsulation data. */
        size_t size; /**< Size of @p data and @p preserve. */
};

Regards
Vamsi

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

      reply	other threads:[~2023-02-15 15:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14  8:51 Vamsi Krishna Attunuru
2023-02-15 15:07 ` Vamsi Krishna Attunuru [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=MWHPR18MB09422917327F58B02070304DA6A39@MWHPR18MB0942.namprd18.prod.outlook.com \
    --to=vattunuru@marvell.com \
    --cc=dev@dpdk.org \
    --cc=orika@nvidia.com \
    /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).