Bart Janssens wrote:
> On Fri, May 2, 2008 at 5:43 AM, Timothy M. Shead <
tshead@...> wrote:
>
>> 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.
>>
>
> Well, if the benchmarks confirm it's worth it, I think we should have
> a system whith properties that keep data on the host that would work
> as follows:
> - Connection between CUDA plugins: Pass data purely in device memory
> - Connection to a non-CUDA pugin: copy data to host
>
A plugin (CUDA or not) executes when a caller (CUDA or not) reads the
value of a property. When the value of the property is read, the caller
must receive an up-to-date value for that property. I'm just
emphasizing that, regardless of any work you guys do with out-of-band
transfers, that's going to be a hard requirement.
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
