From: Stephen Hemminger <stephen@networkplumber.org>
To: Gregory Etelson <getelson@nvidia.com>
Cc: dev@dpdk.org, <mkashani@nvidia.com>,
rasland@nvidia.com, stable@dpdk.org
Subject: Re: [PATCH] testpmd: support meter_mark init_color in indirect list configuration
Date: Mon, 17 Feb 2025 08:24:12 -0800 [thread overview]
Message-ID: <20250217082412.2a45a531@hermes.local> (raw)
In-Reply-To: <20250216140420.216805-1-getelson@nvidia.com>
On Sun, 16 Feb 2025 16:04:20 +0200
Gregory Etelson <getelson@nvidia.com> wrote:
> 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
>
> cc: stable@dpdk.org
>
> Signed-off-by: Gregory Etelson <getelson@nvidia.com>
Patches that are cc to stable need a Fixes tag so that stable
maintainers know what to fix.
But this does not look like stable material since it adds new functionality.
Also, current upstream kernel checkpatch doesn't like # as comment
$ ./devtools/checkpatches.sh
### [PATCH] testpmd: support meter_mark init_color in indirect list configuration
WARNING:COMMIT_COMMENT_SYMBOL: Commit log lines starting with '#' are dropped by git as comments
#19:
# create indirect actions list with meter_mark flow action:
WARNING:COMMIT_COMMENT_SYMBOL: Commit log lines starting with '#' are dropped by git as comments
#24:
# create a flow specific meter_mark init_color configuration:
WARNING:COMMIT_COMMENT_SYMBOL: Commit log lines starting with '#' are dropped by git as comments
#28:
# queue a flow rule with indirect actions list
WARNING:COMMIT_COMMENT_SYMBOL: Commit log lines starting with '#' are dropped by git as comments
#29:
# and flow specific configuration:
WARNING:MISSING_FIXES_TAG: The commit message has 'stable@', perhaps it also needs a 'Fixes:' tag?
total: 0 errors, 5 warnings, 111 lines checked
next prev parent reply other threads:[~2025-02-17 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 14:04 Gregory Etelson
2025-02-17 16:24 ` Stephen Hemminger [this message]
2025-02-17 17:21 ` [PATCH v2] " Gregory Etelson
2025-02-19 18:39 ` Stephen Hemminger
2025-02-20 7:42 ` Ori Kam
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=20250217082412.2a45a531@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=getelson@nvidia.com \
--cc=mkashani@nvidia.com \
--cc=rasland@nvidia.com \
--cc=stable@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).