[dpdk-dev] [PATCH] gpudev: introduce memory API
Thomas Monjalon
thomas at monjalon.net
Thu Jun 3 10:28:50 CEST 2021
03/06/2021 09:47, Jerin Jacob:
> On Thu, Jun 3, 2021 at 2:05 AM Thomas Monjalon <thomas at monjalon.net> wrote:
> > --- a/doc/api/doxy-api-index.md
> > +++ b/doc/api/doxy-api-index.md
> > @@ -21,6 +21,7 @@ The public API headers are grouped by topics:
> > [compressdev] (@ref rte_compressdev.h),
> > [compress] (@ref rte_comp.h),
> > [regexdev] (@ref rte_regexdev.h),
> > + [gpudev] (@ref rte_gpudev.h),
>
> Since this device does not have a queue etc? Shouldn't make it a
> library like mempool with vendor-defined ops?
> Any specific reason for making it a device? The reason why I am asking
> this is, as other DPDK devices as symmetry in queue(s), configure,
> start, stop operation etc.
>
>
> > +
> > +struct rte_gpu_dev {
> > + /* Backing device. */
> > + struct rte_device *device;
>
> See above?
There is a PCI device probed.
I don't understand why it would not be represented as a device.
More information about the dev
mailing list