Thanks Karl,
>From what Barry said, the hypre configure has not done the CUDA stuff so it
can't work right now.
Mark
On Thu, Aug 15, 2019 at 8:57 PM Karl Rupp wrote:
> Hi,
>
> one way to test is to run a sequential example through nv-prof:
> $> nvprof ./ex56 ...
>
>
>
Hi,
one way to test is to run a sequential example through nv-prof:
$> nvprof ./ex56 ...
https://devblogs.nvidia.com/cuda-pro-tip-nvprof-your-handy-universal-gpu-profiler/
If it uses the GPU, then you will get some information on the GPU
kernels called. If it doesn't use the GPU, the list
On Thu, Aug 15, 2019 at 2:34 PM Smith, Barry F. wrote:
>
> Mark,
>
>I don't know how one uses it; we don't yet have an option in hypre.py
> to turn it on.
>
Any ideas about when this might get done?
>
>You should just use regular PETSc matrices and vectors, not CUDA ones.
> Hypre
Mark,
I don't know how one uses it; we don't yet have an option in hypre.py to
turn it on.
You should just use regular PETSc matrices and vectors, not CUDA ones. Hypre
manages all that stuff internally for itsetl.
I don't know how one knows if hypre is using the GPU or not,
I have configured with Hypre on SUMMIT, with cuda, and it ran. I'm now
trying to verify that it used GPUs (I doubt it). Any ideas on how to verify
this? Should I use the cuda vecs and mats, or does Hypre not care. Can I
tell hypre not to use GPUs other than configuring an non-cude PETSc? I'm
not
