Reply – Re: user events, CLEventList
Your Name
or Cancel
In Reply To
Re: user events, CLEventList
— by Sven Gothel Sven Gothel
On 03/09/2012 03:17 AM, notzed [via jogamp] wrote:
> I noticed the forums are a bit quiet for a good few months, has Michael B
> moved on?
Sort of.

> I have a problem regarding user events - although you can create them, wait
> on them and use them as an individual condition to another queued command,
> you cannot add them to an existing event list the way you can accumulate
> events for conditions as with the enqueue commands.
> i.e. i want something like the internal CLEventList.createEvent() but to add
> a user event to the list.  Actually just a simple
> CLEventList.addEvent(CLEvent) which works more or less the same would do.
> I can't just copy the populated event list and create another one with the
> new event added, as the event list is being populated via multiple calls
> from the level above, being passed by reference.
> I want to be able to create a call graph, and have asynchronous java code
> participate in the sequencing transparently.
> I suppose i'll have to write another patch ...
Your use case sounds reasonable I guess.

Sorry, my OpenCL knowledge is still not good enough to give you an answer
here in the way 'this can't work because ..' - or, 'this is great and matches
the architecture.'. I just helped out with the native bindings and
general knowledge a bit.

I am afraid I will tell you the same things here as I did
in our JOAL conversation (patching / unit tests / maintenance),
if you get the idea :)

Since we try to get in some mobile OpenCL 1.1 device for our BOF this year,
I probably have to make a crash course into the current code base.
In May I will have the privileged of 3 weeks 'off',
which means I will have time for this endeavor.
I like to validate whether the current JOCL can be matched to
the OpenCL C++ Wrapper API, if this is not done yet .. etc.

Since you are at least interested, I welcome your support of course.

However, whoever likes to help and support (any project on jogamp)
would need to get familiar w/ the toolchain we use (git, ant, ..).
Otherwise the real maintenance work would become unbearable.

But discussions and knowledge exchange are very valuable contributions
as well, which don't require those things :)

Well, let's see how it goes.


signature.asc (910 bytes) Download Attachment