On Mon, Nov 10, 2025 at 1:11 PM Lukáš Šišmiš <sismis@cesnet.cz> wrote:

> On 11/7/25 17:07, Stephen Hemminger wrote:
> > On Fri, 7 Nov 2025 15:16:28 +0100
> > Lukáš Šišmiš <sismis@cesnet.cz> wrote:
> >
> >> Hello all,
> >>
> >> ## Motivation
> >>
> >>
> >> Before taking either route, I’d like to understand the community’s
> >> preference:
> >> - Do you even see it as a valuable contribution for customer
> applications?
> >> - Can you possibly think of an alternative way to solve the unified
> >> human-readable format conversion? Both on the code level and interface
> >> level.
> >> - Is testpmd code extraction the right long-term solution, even if
> >> disruptive? Should the private DPDK forks be taken into consideration?
> >> Or should I start with a separate lightweight parser and revisit
> >> integration later?
> >>
> >> Any other feedback is welcome


Hi Lukas,
You could try testpmd Command File Functions
<https://doc.dpdk.org/guides-25.07/testpmd_app_ug/testpmd_funcs.html#command-file-functions>
Rte_flows using this method can be created at boot and run time.

   - If testpmd started with the --cmdline-file=FILENAME command line
   argument testpmd will execute all CLI commands contained within the file
   immediately before starting packet forwarding or entering interactive mode.
   - At run-time additional commands can be loaded in bulk by invoking the
   load FILENAME command.


 Best Regards,
Khadem