[petsc-dev] Not possible to do a VecPlaceArray for veccusp
Jeff Hammond
jeff.science at gmail.com
Mon Feb 29 08:03:08 CST 2016
On Monday, February 29, 2016, Karl Rupp <rupp at iue.tuwien.ac.at> wrote:
> Hi Jeff,
>
> > Ok, this is on fairly short notice considering the changes required.
>
>> I recommend to start with copying the CUSP sources and migrate it
>> over to VECCUDA by replacing any use of cusp::array1d to a raw CUDA
>> handle. Operations from CUSP should be replaced by CUBLAS calls.
>>
>>
>> It's hard to imagine any performance benefit from this unless CUSP
>> sucks. What am I missing?
>>
>
> This is not about performance, but about providing the ability for users
> to 'implant' their own memory buffers. CUSP doesn't allow it (which was the
> initial point of this thread).
>
>
Thanks. Sorry I missed that. Given CPU memcpy is an order of magnitude more
bandwidth than PCI offload, I still don't get the point, but I don't need
to.
Jeff
> Best regards,
> Karli
>
--
Jeff Hammond
jeff.science at gmail.com
http://jeffhammond.github.io/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20160229/7ddc39c4/attachment.html>
More information about the petsc-dev
mailing list