DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Alexander Kozyrev <akozyrev@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Slava Ovsiienko <viacheslavo@nvidia.com>,
	Matan Azrad <matan@nvidia.com>,  Ori Kam <orika@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH v3] net/mlx5: support modify field rte flow action
Date: Thu, 28 Jan 2021 09:26:09 +0000
Message-ID: <DM6PR12MB274899027AAA607CD918173BCFBA9@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210128080014.14425-1-akozyrev@nvidia.com>


> -----Original Message-----
> From: Alexander Kozyrev <akozyrev@nvidia.com>
> Sent: Thursday, January 28, 2021 10:00 AM
> To: dev@dpdk.org
> Cc: Raslan Darawsheh <rasland@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>; Ori Kam
> <orika@nvidia.com>
> Subject: [PATCH v3] net/mlx5: support modify field rte flow action
> Add support for new MODIFY_FIELD action to the Mellanox PMD.
> This is the generic API that allows to manipulate any packet
> header field by copying data from another packet field or
> mark, metadata, tag, or immediate value (or pointer to it).
> Since the API is generic and covers a lot of action under its
> umbrella it makes sense to implement all the mechanics gradually
> in order to move to this API for any packet field manipulations
> in the future. This is the first step of RTE flows consolidation.
> The modify field RTE flow action supports three operations: set,
> add and sub. This patch brings to live only the "set" operation.
> Support is provided for any packet header field as well as
> meta/tag/mark and immediate value can be used as a source.
> There are few limitations for this first version of API support:
> - encapsulation levels are not supported, just outermost header
> can be manipulated for now.
> - offsets can only be 4-bytes aligned: 32, 64 and 96 for IPv6.
> - the special ITEM_START ID is not supported as we do not allow
> to cross packet header field boundaries yet.
> Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> ---
> Depends-on: patch-87216
> v1: https://patchwork.dpdk.org/patch/87390/
> v2: Added documentation, addressed comments.
> v3: Corrected header field sizes.

Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      reply	other threads:[~2021-01-28  9:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27  2:48 [dpdk-dev] [PATCH] " Alexander Kozyrev
2021-01-27 11:36 ` Slava Ovsiienko
2021-01-27 14:58   ` Alexander Kozyrev
2021-01-28  7:39 ` [dpdk-dev] [PATCH v2] " Alexander Kozyrev
2021-01-28  8:00 ` [dpdk-dev] [PATCH v3] " Alexander Kozyrev
2021-01-28  9:26   ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM6PR12MB274899027AAA607CD918173BCFBA9@DM6PR12MB2748.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=akozyrev@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=viacheslavo@nvidia.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git