19/10/2021 20:47, Jerin Jacob:
> > As I stated multiple times, let’s start with something simple that works and
> > then think about how to enhance the library/driver.
>
> I have submitted RFC[1] to abstract in a generic way so that
> workload-specific _driver_ aspects are NOT EXPOSED to the application.
>
> The RFC explains with application code, how any workload can be used
> by the application without exposing the driver details.
> Also, shows how to enable a framework to abstract a different form of
> workload acceletor(DPU, GPU, XPU, IPU....)
>
> In order to map to this discussion with RFC:
> You may need to add a new host port for GPU which as
> lib/dwa/rte_dwa_port_host_xxxxx.h and adding new workload as
> lib/dwa/rte_dwa_profile_xxxx.h(Which can be reused by
> all dataplane workload accelerator)
>
> [1] http://mails.dpdk.org/archives/dev/2021-October/226070.html
That's really 2 different points of view:
- expose only some predefined dataplane workloads
- or allow to build any custom worload
