Re: Generic flow string parser

2023-06-05 Thread kumaraparameshwaran rathinavel
On Sun, Apr 30, 2023 at 3:10 AM Thomas Monjalon wrote: > This thread is an API suggestion, it should be discussed in > the developer mailing list (did the Cc here). > > 29/04/2023 16:23, Cliff Burdick: > > > Would rather the flow parser was rewritten as well. Doing open coded > > > parser is much

Re: Generic flow string parser

2023-05-26 Thread Cliff Burdick
On Sat, Apr 29, 2023 at 2:49 PM Cliff Burdick wrote: > > So the only things we need are 2 functions, if I understand well: > > > > int rte_flow_to_text(const struct rte_flow*); > > struct rte_flow *rte_flow_from_text(const char *); > > > > Here I assume the output of rte_flow_from_text() would be

Re: Generic flow string parser

2023-04-29 Thread Cliff Burdick
> So the only things we need are 2 functions, if I understand well: > > int rte_flow_to_text(const struct rte_flow*); > struct rte_flow *rte_flow_from_text(const char *); > > Here I assume the output of rte_flow_from_text() would be a created flow, > meaning it calls rte_flow_create() under the hoo

Re: Generic flow string parser

2023-04-29 Thread Thomas Monjalon
This thread is an API suggestion, it should be discussed in the developer mailing list (did the Cc here). 29/04/2023 16:23, Cliff Burdick: > > Would rather the flow parser was rewritten as well. Doing open coded > > parser is much more error prone and hard to extend versus writing the > > parser i