Hi Evan,
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.
Before going ahead and start designing this system, though, we should
do some more benchmarking on the existing module. I propose splitting
the bitmap_add_entry method in 3 functions:
1. Copy from host memory to device memory
2. Do the calculation on the device
3. Copy from device to host
We can then use the timer from k3dsdk/high_res_timer.h to determine
the overhead of the memory operations, and thus the potential gains of
directly connecting plugins with GPU data.
Cheers,
--
Bart
-------------------------------------------------------------------------
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
