Bruno,

> Is there any reason why you still used the previous way? Is this because
> > your GPU accelerator was launched some years ago so that you are unable
> to
> > use the new simple way?
> The problem with UVM is that it makes it easy to write bad code. I am
> working on a code where we use UVM and it happens quite often that we
> run some code that was intended for the GPU on the CPU. Because of UVM
> it works but at the cost of performance and so it is harder to detect
> that you made a mistake. Another advantage of copying the data
> manually is that you don't hide the costly copy operation. This is
> also the philosophy used in Kokkos. So yes UVM makes writing the code
> easier but you need to be a lot more careful when you write the code
> if you don't want to perform a bunch of useless copy. Of course, if
> you have NVLink it doesn't matter but that only works for POWER chips
> which most people don't have access to.
>

That is a convincing reason for you to do so. I know it now. Thanks!

Let me know once your merger is done so that I can start to install the
deal.II with CUDA in the server I use now.

The CUDA compiler I use now in the server is shown in the following:
[chueh@icycn06 cuda]$ nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2015 NVIDIA Corporation
Built on Tue_Aug_11_14:27:32_CDT_2015
Cuda compilation tools, release 7.5, V7.5.17

Also, I would appreciate to see the detailed instruction on how to install
deal.II together with CUDA, because I don't know how to do that.

Thanks!

Sincerely,

Chih-Che

-- 
The deal.II project is located at http://www.dealii.org/
For mailing list/forum options, see 
https://groups.google.com/d/forum/dealii?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"deal.II User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dealii+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to