Re: [petsc-dev] MATOP_MAT_MULT

2020-05-10 Thread Jose E. Roman
Thanks for the hints. I have modified my branch. I was missing the MatShellSetVecType() call. Now everything works fine and all tests are clean. Jose > El 9 may 2020, a las 21:32, Stefano Zampini > escribió: > > Jose > > I have just pushed an updated example with the MatMat operation, and I

Re: [petsc-dev] MATOP_MAT_MULT

2020-05-10 Thread Stefano Zampini
Glad to hear it works. Anyway, without the MatShellVecSetType call the code was erroring for me, not leaking memory. Where you also providing -vec_type cuda at command line or what? Mark recently noted a similar leak, and I was wondering what was the cause for yours. A MWE would be great. BTW,

Re: [petsc-dev] MATOP_MAT_MULT

2020-05-10 Thread Jose E. Roman
> El 10 may 2020, a las 19:42, Stefano Zampini > escribió: > > Glad to hear it works. Anyway, without the MatShellVecSetType call the code > was erroring for me, not leaking memory. > Where you also providing -vec_type cuda at command line or what? > Mark recently noted a similar leak, and

Re: [petsc-dev] MATOP_MAT_MULT

2020-05-10 Thread Stefano Zampini
> On May 10, 2020, at 8:56 PM, Jose E. Roman wrote: > > > >> El 10 may 2020, a las 19:42, Stefano Zampini >> escribió: >> >> Glad to hear it works. Anyway, without the MatShellVecSetType call the code >> was erroring for me, not leaking memory. >> Where you also providing -vec_type cuda a