[petsc-dev] Current status: GPUs for PETSc

[Karl Rupp]

>     The copy_to_cpu-part could be managed via page-locked memory, yet I
>     still have to investigate its robustness. It is certainly a nice
>     option for APUs, because it has zero overhead. The only drawback is
>     that APUs just lack performance in general...
>
>     Overall, I don't want to give away the robustness you described
>     above. There will always be some operations that work better on the
>     CPU, while others work better on accelerators, so hopping between
>     them is (unfortunately) rather the rule than the exception in real
>     world applications.
>
>
> Okay, then I have a procedural question. Should we write about this for
> the GPU book, or just describe the
> current state of affairs?

Considering that I wanted to contact you anyway with respect to help on 
the write-up for the book: Can we postpone this decision to around 
November 20th? I guess I will have have a much clearer picture on the 
topic then.

Best regards,
Karli