Re: CUDA benchmarking

Bart Janssens wrote:
> I've been going through the CUDA docs, and from the looks of it there
> are no technical obstacles to creating a chain of K-3D plugins that
> keep the main part of their data (i.e. a mesh, bitmap, ...) in GPU
> memory throughout the pipeline. I especially like the fact that CUDA
> can directly access OpenGL buffer objects, which means the result of
> the pipeline calculation can be displayed directly.
>  
Forgot to mention my skepticism on this issue earlier.  When a call to
iproperty::property_value() returns, its result must be completely
up-to-date, otherwise the caller will fail.  Thus, a CUDA plugin will
still have to marshal data back to the host whenever the pipeline executes.

FWIW, I didn't really expect much of an improvement in image-processing
speed - just like our experiments in threading, we're going to have to
tackle larger problems before we see real improvements in performance.

Cheers,
Tim


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
K3d-development mailing list
K3d-development@...
https://lists.sourceforge.net/lists/listinfo/k3d-development