From: Stephen Hemminger <stephen@networkplumber.org>
To: "Ajmera, Megha" <megha.ajmera@intel.com>
Cc: Konstantin Ananyev <konstantin.ananyev@huawei.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"Shetty, Praveen" <praveen.shetty@intel.com>,
"Singh, Aman Deep" <aman.deep.singh@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH v2] app/test-pmd: add generic PROG action parser support
Date: Sun, 31 May 2026 22:07:24 -0700 [thread overview]
Message-ID: <20260531220724.0070314c@phoenix.local> (raw)
In-Reply-To: <MW4PR11MB589273F3A331E94D0876900D97152@MW4PR11MB5892.namprd11.prod.outlook.com>
On Mon, 1 Jun 2026 04:33:42 +0000
"Ajmera, Megha" <megha.ajmera@intel.com> wrote:
> >
> > For my own curiosity: how user can define his own PROG action?
> > Is it supposed to be programmed and uplodaded to the NIC by some external tool
> > (P4 compiler)?
> > Or does it refer to the set of some predefined functions that given firmware
> > supports?
> > Or ... ?
> > Sorry for probably naive questions, but I found is nearly zero information inside
> > DPDK docs about how PROG action supposed to work.
>
> PROG in rte_flow is currently a vendor-defined action interface (name + arguments), not a generic DPDK programming model by itself.
Supporting vendor specific extensions like this should be actively discouraged.
There is a reason DPDK succeeded and OpenDataplane did not.
next prev parent reply other threads:[~2026-06-01 5:07 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
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 [this message]
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=20260531220724.0070314c@phoenix.local \
--to=stephen@networkplumber.org \
--cc=aman.deep.singh@intel.com \
--cc=bruce.richardson@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--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