<snip> > > How about moving this as separate library(pipeline dev) with driver(plugin) > interface > and librte_pipeline based API being used as one plugin/driver. This will > enable us > to hook another HW based or HW-SW combination of plugins in future.
This is exactly what we are looking to do. The PDEV API is meant to be generic, while the current librte_pipeline API is limited to SW only. The intention is to transform the current librte_pipeline code into driver/plugin for the new PDEV API, with hopefully lots of other devices supporting PDEV through their own drivers. > > Eventdev has capability to create pipeline that can be add in future > as plugin/driver. The code to deal with rte_tm etc in plugin, you can > make it as common code in the library. So that new plugin can be created > based eventdev > + other building blocks such as rte_tm. > It would be great to be able to expose some/all of the eventdev features through PDEV API, let's look at this together. > > /Jerin
