From: Stephen Hemminger <stephen@networkplumber.org>
To: "Lukáš Šišmiš" <sismis@dyna-nic.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
dev@dpdk.org, Ori Kam <orika@nvidia.com>
Subject: Re: [PATCH v10 3/6] flow_parser: add shared parser library
Date: Fri, 13 Feb 2026 11:16:36 -0800 [thread overview]
Message-ID: <20260213111636.45d01a2d@phoenix.local> (raw)
In-Reply-To: <CAPQRu6EAKR59BGgRFAr=eWuQr+=3z14+xdCkbZMvfhM5K8bN0A@mail.gmail.com>
On Fri, 13 Feb 2026 08:46:04 +0100
Lukáš Šišmiš <sismis@dyna-nic.com> wrote:
> Ok, I can move it there then. Should I proceed with Patch v11 - that would
> include moving the ethdev directory and addressing the kernel's checkpatch
> issues?
>
> The initializer doesn't seem like a bad idea. I didn't know about that one.
> The parser_ops are not needed for purely parsing, but to remain compatible
> with the testpmd's code, which is using, e.g., the hints on the commandline
> I added parser_ops.
> The simple public library API is for converting strings to rte_flow
> structures,
> the parser_ops is for hooking up the testpmd.
Testpmd can change as needed.
In general testpmd shouldn't be using "special" API's; that would indicate
a architecture issue.
next prev parent reply other threads:[~2026-02-13 19:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 11:36 [PATCH v10 0/6] flow_parser: add shared parser library Lukas Sismis
2026-02-02 11:36 ` [PATCH v10 1/6] cmdline: include stddef.h for MSVC compatibility Lukas Sismis
2026-02-02 11:36 ` [PATCH v10 2/6] ethdev: add RSS type helper APIs Lukas Sismis
2026-02-17 14:40 ` Stephen Hemminger
2026-02-02 11:36 ` [PATCH v10 4/6] app/testpmd: use shared flow parser library Lukas Sismis
2026-02-02 11:36 ` [PATCH v10 5/6] examples/flow_parsing: add flow parser demo Lukas Sismis
2026-02-02 11:36 ` [PATCH v10 6/6] test: add flow parser library functional tests Lukas Sismis
2026-02-02 18:37 ` [PATCH v10 0/6] flow_parser: add shared parser library Stephen Hemminger
[not found] ` <20260202113659.24052-4-sismis@dyna-nic.com>
2026-02-02 20:03 ` [PATCH v10 3/6] " Stephen Hemminger
2026-02-03 8:34 ` Lukáš Šišmiš
2026-02-04 14:53 ` Stephen Hemminger
2026-02-06 14:01 ` Thomas Monjalon
2026-02-06 15:40 ` Lukáš Šišmiš
2026-02-13 0:43 ` Stephen Hemminger
2026-02-13 7:46 ` Lukáš Šišmiš
2026-02-13 19:16 ` Stephen Hemminger [this message]
2026-02-14 4:35 ` Stephen Hemminger
2026-02-10 14:44 ` Stephen Hemminger
2026-02-10 14:45 ` [PATCH v10 0/6] " Stephen Hemminger
2026-02-12 8:56 ` Lukáš Šišmiš
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=20260213111636.45d01a2d@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=orika@nvidia.com \
--cc=sismis@dyna-nic.com \
--cc=thomas@monjalon.net \
/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