CLBuffer - remote machine access

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

CLBuffer - remote machine access

suleman
Hi,

I want to use the CLBuffer  created on some remote machine (with GPUs), and want to access via RMI, but the CLBuffer is not serializable.

thanks
Reply | Threaded
Open this post in threaded view
|

Re: CLBuffer - remote machine access

Wibowit
I think you should make a proxy for that. I doubt drivers for popular GPUs support remote buffers.
Reply | Threaded
Open this post in threaded view
|

Re: CLBuffer - remote machine access

suleman
Hi,

Thanks for your reply.

Is the ID field of a CLBuffer is unigue (is distinct for each created CLBuffer object), if this is the case then i can use this as the key for Proxy memory objects (CLBuffer)
Reply | Threaded
Open this post in threaded view
|

Re: CLBuffer - remote machine access

Michael Bien
  The ID of a CLBuffer is a pointer to the cl_mem object which should be
unique for every native OpenCL buffer or even for sub-buffers. If you
are using multiple CLBuffer views on the same native buffer all those
views will have the same native buffer ID since they share the same buffer.

-michael

On 04/11/2011 11:44 AM, suleman [via jogamp] wrote:
> Hi,
>
> Thanks for your reply.
>
> Is the ID field of a CLBuffer is unigue (is distinct for each created
> CLBuffer object), if this is the case then i can use this as the key for
> Proxy memory objects (CLBuffer)