DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Lukas Sismis <sismis@dyna-nic.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v1 1/5] flow_parser: add shared parser library
Date: Tue, 6 Jan 2026 08:35:26 -0800	[thread overview]
Message-ID: <20260106083526.03e9c258@phoenix.local> (raw)
In-Reply-To: <20260105213025.749383-2-sismis@dyna-nic.com>

On Mon,  5 Jan 2026 22:30:19 +0100
Lukas Sismis <sismis@dyna-nic.com> wrote:

> Introduce librte_flow_parser as an optional, experimental library
> exposing the testpmd flow CLI parser as a reusable component.
> 
> The library provides:
> - rte_flow_parser_init(): Initialize parser with operation callbacks
> - rte_flow_parser_parse(): Parse flow command strings into output
> - rte_flow_parser_run(): Parse and execute via registered callbacks
> - Helper functions for parsing pattern/action/attribute strings
> 
> The parser uses a single global instance design for simplicity.
> All parsing state is internal to the library. Callbacks are invoked
> for flow create, destroy, validate, query and other flow operations.
> 
> This enables applications to reuse testpmd's well-tested flow syntax
> without duplicating the parser implementation.
> 
> Signed-off-by: Lukas Sismis <sismis@dyna-nic.com>
> ---

Any new feature like this is required to add a new standalone test
to the functional tests.

  reply	other threads:[~2026-01-06 16:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-05 21:30 [PATCH v1 0/5] " Lukas Sismis
2026-01-05 21:30 ` [PATCH v1 1/5] " Lukas Sismis
2026-01-06 16:35   ` Stephen Hemminger [this message]
2026-01-05 21:30 ` [PATCH v1 2/5] app/testpmd: integrate shared flow " Lukas Sismis
2026-01-05 21:30 ` [PATCH v1 3/5] examples/flow_parsing: add flow parser demo Lukas Sismis
2026-01-05 21:30 ` [PATCH v1 4/5] test: add flow parser unit tests Lukas Sismis
2026-01-06 16:37   ` Stephen Hemminger
2026-01-05 21:30 ` [PATCH v1 5/5] doc: add flow parser library maintainers Lukas Sismis

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=20260106083526.03e9c258@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=sismis@dyna-nic.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).