Re: [dpdk-dev] [PATCH] raw/common: introduce the Multi-function API

[Thomas Monjalon <thomas@monjalon.net>]

Hi,

02/04/2020 11:46, O'loingsigh, Mairtin:
> From: Thomas Monjalon <thomas@monjalon.net> 
> > 16/03/2020 20:21, Mairtin o Loingsigh:
> > > Multi-function API allows user to chain xforms of various types
> > > together in a single operation
> > 
> > Please could you elaborate a bit more?
> > Which problem are you trying to address?
> > What is the design?
> > How it can be used?
> > 
> > For such feature proposal, I recommend a design discussion before starting
> > the development.
> 
> The purpose of the Multi-function API is to enable a broader set of
> transforms that aren't compression /crypto specific (CRC for example)
> We had quite a few discussions on Multi-function in the mails below 
> 
> http://mails.dpdk.org/archives/dev/2020-February/157045.html
> http://mails.dpdk.org/archives/dev/2020-March/159189.html

OK

Personally I did not have time yet to dive into this design.
But as a first impression, I feel it is not the right API.
DPDK is based on classes: ethdev, crypto, compress, baseband, regex
I want to understand why your features cannot fit in a class.


> The v2 patchset will be ready for this in the coming days
> and we will include a cover-letter describing the feature
> and referencing back to the RFC discussion this time around

I feel we will need a lot of time to discuss the design.
If you don't see any consensus on the design in the mailing list,
you should request an opinion from the Technical Board.

This feature is not a priority for 20.05 release.
By the way, it has not been announced in any roadmap.