DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ori Kam <orika@nvidia.com>
To: Gregory Etelson <getelson@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Gregory Etelson <getelson@nvidia.com>,
	Maayan Kashani <mkashani@nvidia.com>,
	Raslan Darawsheh <rasland@nvidia.com>
Subject: RE: [PATCH v2] testpmd: support meter_mark init_color in indirect list configuration
Date: Thu, 20 Feb 2025 07:42:28 +0000	[thread overview]
Message-ID: <PH0PR12MB5679E5458D54F7A938F6705BD6C42@PH0PR12MB5679.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20250217172111.67655-1-getelson@nvidia.com>



> -----Original Message-----
> From: Gregory Etelson <getelson@nvidia.com>
> Sent: Monday, February 17, 2025 7:21 PM
> 
> Flow actions parameters in indirect actions list are created as
> read-only and shared between all flows that reference that indirect
> list.
> 
> If a flow rule needs to apply rule specific actions list parameters it
> does it with the indirect actions list conf parameter.
> 
> The patch allows flow rule to set meter_mark init_color value when
> meter_mark action was created in indirect actions list.
> 
> Example:
> 
> // create indirect actions list with meter_mark flow action:
> testpmd> flow indirect_action 0 create action_id 10 ingress \
>   list actions meter_mark mtr_profile 20 \
>   mtr_state 1 mtr_color_mode 1 / end
> 
> // create a flow specific meter_mark init_color configuration:
> testpmd> flow indirect_action 0 create action_id 11 flow_conf \
>    actions meter_mark_conf mtr_update_init_color red / end
> 
> // queue a flow rule with indirect actions list
> // and flow specific configuration:
> testpmd> flow queue 0 create 0 template_table 1 pattern_template 0 \
>    actions_template 0 postpone no pattern eth / ipv4 / udp / end \
>    actions indirect_list handle 10 conf 11 / \
>    jump group 10 / end
> 
> Signed-off-by: Gregory Etelson <getelson@nvidia.com>
> ---
> v2: Fix commit log.
> ---

Acked-by: Ori Kam <orika@nvidia.com>
Best,
Ori

  parent reply	other threads:[~2025-02-20  7:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-16 14:04 [PATCH] " Gregory Etelson
2025-02-17 16:24 ` Stephen Hemminger
2025-02-17 17:21 ` [PATCH v2] " Gregory Etelson
2025-02-19 18:39   ` Stephen Hemminger
2025-02-20  7:42   ` Ori Kam [this message]
2025-02-18 10:49 ` [PATCH] config/arm: update NVIDIA BlueField-3 configuration Gregory Etelson
2025-02-19 16:35   ` Wathsala Wathawana Vithanage
2025-02-19 17:32     ` Thomas Monjalon

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=PH0PR12MB5679E5458D54F7A938F6705BD6C42@PH0PR12MB5679.namprd12.prod.outlook.com \
    --to=orika@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=getelson@nvidia.com \
    --cc=mkashani@nvidia.com \
    --cc=rasland@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).