From: Stephen Hemminger <stephen@networkplumber.org>
To: Megha Ajmera <megha.ajmera@intel.com>
Cc: bruce.richardson@intel.com, cristian.dumitrescu@intel.com,
praveen.shetty@intel.com, dev@dpdk.org
Subject: Re: [PATCH v2] app/test-pmd: add generic PROG action parser support
Date: Tue, 26 May 2026 12:22:18 -0700 [thread overview]
Message-ID: <20260526122218.1c29d917@phoenix.local> (raw)
In-Reply-To: <20260521101354.726240-1-megha.ajmera@intel.com>
On Thu, 21 May 2026 15:43:54 +0530
Megha Ajmera <megha.ajmera@intel.com> wrote:
> Add parser support for a generic PROG flow action in testpmd.
>
> The update adds CLI tokens and parsing logic for program name and
> argument tuples (name, size, value), enabling programmable action
> configuration through the flow command interface.
>
> Example flow rule:
> flow create 0 ingress pattern eth / end actions prog name my_prog
> argument name arg0 size 4 value 10 / end
>
> Signed-off-by: Megha Ajmera <megha.ajmera@intel.com>
> Signed-off-by: Praveen Shetty <praveen.shetty@intel.com>
> ---
This looks like a third attempt to parse text into rte_flow.
Not sure how this fits in and why it would be useful?
next prev parent reply other threads:[~2026-05-26 19:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 5:56 [PATCH] app/test-pmd: add generic PROG action parser support Megha Ajmera
2026-05-21 10:13 ` [PATCH v2] " Megha Ajmera
2026-05-26 19:22 ` Stephen Hemminger [this message]
2026-05-27 9:20 ` Ajmera, Megha
2026-05-27 11:51 ` Konstantin Ananyev
2026-06-01 4:33 ` Ajmera, Megha
2026-06-01 5:07 ` Stephen Hemminger
2026-06-02 7:35 ` Konstantin Ananyev
2026-06-02 17:11 ` Ajmera, Megha
2026-06-03 6:53 ` Konstantin Ananyev
2026-05-27 15:41 ` Stephen Hemminger
2026-06-01 4:27 ` Ajmera, Megha
2026-06-01 4:16 ` [PATCH v3] " Megha Ajmera
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=20260526122218.1c29d917@phoenix.local \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=megha.ajmera@intel.com \
--cc=praveen.shetty@intel.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