4 ms·
The framework allows for partial data updates - for instance for a 3D renderer it suffices the push the new position to the GPU whilst the vertex data remains i
by Gladdyu 11y ago
The framework allows for partial data updates - for instance for a 3D renderer it suffices the push the new position to the GPU whilst the vertex data remains in GPU memory. If you invoke the kernel function again it will not recompile the kernel nor reupload the vertex data.
The DAG idea sounds fun to build and very useful - I have some spare time anyway so I'll see what I can whip up. As for the command line interface - It too sounds pretty useful and it should only be a bit of parsing as all the OpenCL related code as been written already, but ufo-launch already performs pretty much the same function so it's not very high on my todo list.
- exDM69 11y ago> The framework allows for partial data updates Good! Additionally, it would be useful to memory map buffers and allow using raw pointers in addition to std::vectors. But more importantly, it would be necessary to use the output of one kernel as the input of another kernel invocation. Anyway, build it to suit your use case primarily. Happy hacking!
- Polytonic 11y agoSorry to keep plugging my stuff, but you might be interested in this ... https://github.com/Polytonic/Chlorine https://github.com/Polytonic/Chlorine No raw pointers, but you can use C arrays (was that what you meant by raw pointers?).