I am not sure if anyone has tried putting Piston and Coprocessing together yet. If so I would like to hear about it. If not and someone is trying, I wouldn't mind getting involved in that effort.
But yes Mark you are right. As it stands there will be a round trip in between the simulation and vis stages. We will have to extend Catalyst with the ability to create a vtkPistonDataObject that refers to the data already on the GPU in order to avoid it. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Aug 20, 2013 at 12:45 PM, Vanmoer, Mark W <[email protected]>wrote: > Hello, for a CUDA application with coprocessing, is it correct that > between a simulation step and coprocessing that the data will make a > roundtrip from the device to the host and back to the device, since parts > of the vis pipeline run on the CPU?**** > > ** ** > > Can Piston work with coprocessing, would that avoid this round-trip? **** > > ** ** > > How about for Xeon Phis?**** > > ** ** > > Thanks,**** > > Mark**** > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/mailman/listinfo/paraview > >
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
