On Sun, Jun 6, 2021 at 6:44 AM Honnappa Nagarahalli
wrote:
>
>
>
> > > >
> > > > 04/06/2021 17:20, Jerin Jacob:
> > > > > On Fri, Jun 4, 2021 at 7:39 PM Thomas Monjalon
> > wrote:
> > > > > > 04/06/2021 15:59, Andrew Rybchenko:
> > > > > > > On 6/4/21 4:18 PM, Thomas Monjalon wrote:
> > > > > >
> > >
> > > 04/06/2021 17:20, Jerin Jacob:
> > > > On Fri, Jun 4, 2021 at 7:39 PM Thomas Monjalon
> wrote:
> > > > > 04/06/2021 15:59, Andrew Rybchenko:
> > > > > > On 6/4/21 4:18 PM, Thomas Monjalon wrote:
> > > > > > > 04/06/2021 15:05, Andrew Rybchenko:
> > > > > > >> On 6/4/21 3:46 PM, Thoma
>
> From: Elena Agostini
>
> The new library gpudev is for dealing with GPU from a DPDK application in a
> vendor-agnostic way.
It would be good to explain how the application using GPU+DPDK would look like.
Which parts of the workload need DPDK's support?
Any requirements on co-existence of
> -Original Message-
> From: Thomas Monjalon
> Sent: Saturday, June 5, 2021 15:49
> To: Wang, Haiyue
> Cc: dev@dpdk.org; Elena Agostini ;
> andrew.rybche...@oktetlabs.ru; Yigit, Ferruh
> ; jer...@marvell.com
> Subject: Re: [dpdk-dev] [PATCH] gpudev: introduce memory API
>
> 04/06/2021 2
04/06/2021 20:04, Wang, Haiyue:
> From: Thomas Monjalon
> > 04/06/2021 15:25, Wang, Haiyue:
> > > From: Thomas Monjalon
> > > > Another question is about the function rte_gpu_free().
> > > > How do we recognize that a memory chunk is from the CPU and GPU visible,
> > > > or just from GPU?
> > > >
5 matches
Mail list logo