DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Ananyev <konstantin.ananyev@huawei.com>
To: "Ajmera, Megha" <megha.ajmera@intel.com>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: "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: Wed, 27 May 2026 11:51:11 +0000	[thread overview]
Message-ID: <03ab65f8b69a4018aad7afcc88f337e1@huawei.com> (raw)
In-Reply-To: <MW4PR11MB5892D90B2AF860214FB57F4D97082@MW4PR11MB5892.namprd11.prod.outlook.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?
> 
> Thanks for the feedback.
> I wanted to clarify the intent of this patch. The backend support for the PROG
> action already exists in the PMD. This patch is focused on adding the
> corresponding frontend (testpmd) parser support so that users can configure
> and exercise this functionality via CLI.
> The motivation here is to enable configuration of programmable actions that are
> already supported in the backend but cannot currently be invoked through
> testpmd. With this addition, new actions that are exposed through PROG can be
> configured using the flow command interface.

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.
Thanks
Konstantin

  reply	other threads:[~2026-05-27 11:51 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 [this message]
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=03ab65f8b69a4018aad7afcc88f337e1@huawei.com \
    --to=konstantin.ananyev@huawei.com \
    --cc=aman.deep.singh@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=megha.ajmera@intel.com \
    --cc=praveen.shetty@intel.com \
    --cc=stephen@networkplumber.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